Claire Foster

Results 128 issues of Claire Foster

DataSets is kind of hard to use with Distributed.jl. The main usability problem is that it's impossible to deserialize handles like Blob or BlobTree when they rely on the availability...

## Background I've been looking at Circutscape.jl as an interesting use case for DataSets.jl. Here's a design for how DataSets could support circuitscape user workflows. Circuitscape is an interesting case...

Hopefully this should avoid most invalidations caused by loading other packages as discussed in https://github.com/JuliaLang/JuliaSyntax.jl/issues/252. Also refactor/replace the NEW_KEYBINDINGS global as it's hard to follow where this is added to,...

As requested in https://github.com/JuliaLang/JuliaSyntax.jl/issues/312#issuecomment-1616377851, here's a concrete description of roughly what needs doing (in reference to files over at JuliaLang/julia) to tackle the next parts of the compiler frontend. *...

design

Import paths with a prefixed pair of dots should parse as follows: ```julia julia> JuliaSyntax.parse(SyntaxNode, "import ..A") line:col│ tree │ file_name 1:1 │[import] 1:7 │ [.] 1:8 │ . 1:9...

bug
tokenizer
parser
intro issue

Likely due to #325 we have the following difference: ```julia julia> dump(parsestmt(Expr, "x.[y]")) Expr head: Symbol . args: Array{Any}((2,)) 1: Symbol x 2: QuoteNode value: Expr head: Symbol vect args:...

Tests are now failing on `main` due to a parsing inconsistency between JuliaSyntax and the flisp parser and a line in the JuliaLang/julia tests at https://github.com/JuliaLang/julia/blob/6e23543bc477eb46e5fc8d5cab119190b990ed7c/test/core.jl#L8070 This can be reduced...

Using the tools from #379 uncovers several bugs. For example ```julia fuzz_test(try_parseall_failure, product_token_fuzz(cutdown_tokens, 2)) fuzz_test(try_hook_failure, product_token_fuzz(cutdown_tokens, 2)) fuzz_test(try_parseall_failure, random_token_fuzz(cutdown_tokens, 10, 10_000_000)) ``` Some errors found with this: ### Parser errors...

bug

A super hacky, quick implementation of "pipefirst / pipelast" ideas inspired by https://discourse.julialang.org/t/fixing-the-piping-chaining-issue Tiny demo: ```julia julia> 1:10 />> filter(isodd) />> map(z->z^2) 5-element Vector{Int64}: 1 9 25 49 81 ```...

syntax change

Parsing large, completely malformed files takes a long time. I think it'd probably make sense to detect "parsing this file is a complete disaster, it's probably not even valid Julia...