This is pretty nice and intuitive! What is odd is how you don't need spaces between string identifiers
intintint does the same as int int int, 3 integrals
del becomes a del symbol, delt becomes a del symbol plus a t, delta becomes a delta symbol
rhoint: will it become rh + oint (circular integral), or rho + int? It happens to become rho + int here, but does it specify that in its specification?
deltau: will it become del + tau, or delta + u? it happens to become delta + u here. Opposite of the rhoint case about where it chose to make both things a rendered symbol
So it's inconsistent parsing rules, simply requiring spaces between textual identifiers would make it more logical :)
Also, what is now => and lArr could make more sense as ==> and <==. Also sad that <- or <-- doesn't work for left arrow.
intintint does the same as int int int, 3 integrals
del becomes a del symbol, delt becomes a del symbol plus a t, delta becomes a delta symbol
rhoint: will it become rh + oint (circular integral), or rho + int? It happens to become rho + int here, but does it specify that in its specification?
deltau: will it become del + tau, or delta + u? it happens to become delta + u here. Opposite of the rhoint case about where it chose to make both things a rendered symbol
So it's inconsistent parsing rules, simply requiring spaces between textual identifiers would make it more logical :)
Also, what is now => and lArr could make more sense as ==> and <==. Also sad that <- or <-- doesn't work for left arrow.