Somewhat oddly (given the focus of the language and the fact that I'm doing Physics) I haven't spent much time on the numerical side. Partly that's because there's plenty of people doing that already, and I think Julia has a lot of potential as a general purpose language as long as the libraries (like Lazy.jl) are there.
My main projects for the foreseeable future are Jewel and perhaps a Markdown parser (which is Jewel-related). So what kinds of things are you interested in using it for, then?
span.cm-bracket. Since everything else does work it's no big deal (one can just set the default color and change every other color), but I thought I'd notify you.
end, although there might be something strange going on with my LT installation since I was pretty sure that's new behaviour
printlnetc treated as builtin? I don't quite see why Types, special values like
Infand those functions should be treated the same.
columncheck is mine though, the idea is to treat both
foo() =as definitions
columncheck: I totally forgot about that way to define functions! It does make sense to style them the same as the ones defined by
function, although that check is not enough. Even a function call starting in column zero will trigger the definition-style, so a check whether there's an
=after the function call should probably be added. That should cover all cases, but I'm not experienced enough in Julia to be sure about that.
foo(...) = ...is that you have to parse everything between the brackets before you get to the
=, and even then it breaks when the
=is on a new line. I might make it more precise in future but for now I think overshooting is probably better than undershooting
nvariables in the current scope and emit the style