File tree Expand file tree Collapse file tree 1 file changed +19
-0
lines changed Expand file tree Collapse file tree 1 file changed +19
-0
lines changed Original file line number Diff line number Diff line change @@ -1205,3 +1205,22 @@ indentation from the syntax tree? Source formatting involves a big pile of
1205
1205
heuristics to get something which "looks nice"... and ML systems have become
1206
1206
very good at heuristics. Also, we've got huge piles of training data — just
1207
1207
choose some high quality, tastefully hand-formatted libraries.
1208
+
1209
+ # Getting involved
1210
+
1211
+ For people who want to help improve Julia's error messages by contributing to
1212
+ JuliaSyntax, I'd suggest looking through the issue list at
1213
+ https://github.com/JuliaLang/JuliaSyntax.jl/issues and choosing a small issue
1214
+ or two to work on to familiarize yourself with the code. Anything marked with
1215
+ the labels `intro issue` or `bug` might be a good place to start.
1216
+
1217
+ Also watching the 2022 JuliaCon talk and reading this document is probably good
1218
+ for an overview.
1219
+
1220
+ As of March 2023, we've got really good positional tracking within the source,
1221
+ but JuliaSyntax really needs a better system for parser recovery before the
1222
+ errors are really nice. This requires some research. For example, you could
1223
+ read up on how rust-analyzer does recovery, or rslint - both these are
1224
+ event-based recursive decent parsers with similar structure to JuliaSyntax
1225
+ (though in Rust). I also want to investigate whether we can do data-driven
1226
+ parser recovery using an ML technique. But again, this is a research project.
You can’t perform that action at this time.
0 commit comments