Paul Zinn-Justin
Paul Zinn-Justin
just trying to understand the latest changes. now this works: ``` new Error from 42 ``` but what happens under the hood? also why the need for a special `new...
I might stop here, to keep this PR relatively small and to avoid the more controversial items on my list.
sure.
though it would be nice to have a common ancestor, since I don't want to have two different methods `makeKeyword` and `makeOperator` which would do the exact same thing.
> I guess what I'm saying is we should _not_ have `makeKeyword` at all, since by definition keywords are the preserved symbols. > > edit: to clarify, a `makeKeyword` function...
to recap: two types of `Keyword` exist: 1. the ones that look like normal (alphanumeric) symbols, like `and` 2. the ones made of special characters, like `**`. These are the...
oh yeah this PR also fixes this silly bug: `getGlobalSymbol ""`
sure, I'm happy to name it something else. but the point is, for all practical purposes, in that example, `and` and `implies` behave in the exact same way, and therefore...
> > for all practical purposes, in that example, `and` and `implies` behave in the exact same way, and therefore should probably have the same class. > > Then users...
actually, it makes no difference whether the keyword is alphanumeric or not. there will be a conflict if two packages define the same keyword. Right now it's a non issue...