Steve Kelly
Steve Kelly
I often find I need to reference this to fix stdlib compats: https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958 It would be helpful in the failure error message to suggest a stdlib compat based on the...
It seems as though this line is triggering some type instability: https://github.com/JuliaGeometry/TetGen.jl/blob/4ce1bd589ebfc5a3eb14f729ae5f9657274df7d6/src/cppwrapper.jl#L290-L296 One solution towards this is parsing of the arguments to determine the actual type parameters in the `tetrahedralize`...
The current implementation registers multiple `atexit` handlers because the `git_libgit2_init` `ccall` returns the number of inits that have happened. So, every time we run `ensure_initialized` (which is frequent), we register...
See below, we start getting a stack trace from the following definition in `REPL`. This seems to start with a failure to handle the following incomplete type definitions: https://github.com/JuliaLang/julia/blob/64de065a183ac70bb049f7f9e30d790f8845dd2b/stdlib/REPL/src/REPL.jl#L570-L599 ```...
First, @rohitvarkey I can't express how great this package is for my work. Hopefully some cool demos will come out of this. Thanks again! Here I am expecting the text...
GC data
It would be nice to see the garbage collection data (time and bytes). The time macro in Base supports this. See: https://github.com/JuliaLang/julia/blob/e9948b4b65140d3e82006bc222834ddf88cbbc9b/base/util.jl#L51-L63
These hooks are usually registered at module `__init__`, partially to make the code easier to reason about. Though this now has greater significance with improved static compilation techniques, since the...
otherwise we run code at module load each time.
Notice on http://docs.julialang.org/en/latest/stdlib/file/ http://docs.julialang.org/en/latest/stdlib/file/#Base.expanduser Renders the arrow (->) as a single character. But for a multiple return (f() -> (x,y)), this is not the case: http://docs.julialang.org/en/latest/stdlib/file/#Base.splitdrive
`run_tests` is very useful for orchestrating tests in isolated contexts, and may make sense to document further. However, this is a minimal start for reference in the REPL.