Some of them are binary but not source incompatibilities so sure, that’s the whole point, I think. But some are just broken under 2.13, such as scoverage.
I have other issues with fury, which I already brought up with @propensive, and might be show stoppers for my specific needs
-
Storing code as text (rather than as a parsed AST) is a disaster; this is only one symptom of many.
Maybe you could even annotate the AST with enough metadata to achieve something close to the poetry @tpolecat talks of...
-
-
As an example, between any two tokens, there is a very limited number of viable whitespace options. It shouldn't be possible to encode whitespace other than these. Higher-level formatting options would be possible.
-
well, it depends of the surrounding token, b/c really, these "=>", "<-", ",", etc must be aligned :)
- Show replies
New conversation -
-
-
Yes! And the annotation should be *separate* from the underlying AST - such that you can choose to apply it in the context of your preferred formatter, or choose a different customization.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.