@dan_abramov @jlongster @babeljs @gnijor No, you need to invent new syntax for sweet.js macros which is very hostile imo
-
-
Replying to @sebmck
@dan_abramov@jlongster@gnijor the types of transforms you can do is also quite basic. Doesn't really lend itself to complex stuff.1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@dan_abramov@gnijor this is completely wrong... advanced systems like Racket (which sweet is based on) can even do type inference6 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster@dan_abramov@gnijor With macros it's extremely brittle and if you venture even slightly from what the macro describes it fails.6 replies 0 retweets 0 likes -
Replying to @sebmck
@jlongster@dan_abramov@gnijor Also you have no access to scope tracking etc. Extremely limited in what you can do.1 reply 0 retweets 0 likes -
Replying to @sebmck
@sebmck@dan_abramov@gnijor (last min correction: you can have access to scope :))1 reply 0 retweets 0 likes -
Replying to @jlongster
@jlongster@dan_abramov@gnijor How would you check if say there's a `bar` binding in the current scope?2 replies 0 retweets 0 likes -
Replying to @sebmck
@sebmck@dan_abramov@gnijor bar in getLocalBindings()2 replies 0 retweets 0 likes -
Replying to @jlongster
@jlongster@dan_abramov@gnijor Mainly the lack of comments and massive methods like https://github.com/mozilla/sweet.js/blob/master/src/expander.js#L1022-1764 …3 replies 0 retweets 1 like -
Replying to @sebmck
@sebmck@dan_abramov@gnijor I <3 compilers for stuff like es6->es5, but macros for lots of other stuff3 replies 0 retweets 0 likes
@jlongster @dan_abramov @gnijor Thanks for the info! Definently cool stuff. I'm admittedly ignorant so I appreciate the correction.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 