Koki Fushimi
Koki Fushimi
I read `src/buffer_input.jl` and `src/scanner.jl` many times. A few days after sending this pull request, I noticed a few things. The variable name `length` is used as the 2 following...
I propose: * `parseonly` for parsing the only single document in a YAML file, if the YAML file consists of 0 or 2 or more than 2 documents (`n ==...
The deprecation code will be: ```julia # YAML.jl v0.5 @deprecate load parsefirst @deprecate load_all parse @deprecate load_file parsefirstfile @deprecate load_all_file parsefile ```
YAML spec uses the words _load_ and _dump_ for converting a YAML to a native data and the reverse process.
If the deprecation is completed, I think it may be good to prepare `load` and `dump` for aliases of reading and writing.
Julia base exports the name `parse` so we need to replace existing `parse` to `Base.parse` to define `parse` of the module `YAML`.
It's the most important interface, it will be good to gather broad opinions.
First, we should solve https://github.com/JuliaData/YAML.jl/issues/151, then let's get started on this.
My workaround on macOS 15 (Sequoia) after reading dazzatronus’ post: 1. `brew uninstall espanso` (Espanso 2.2.7) 2. `brew install espanso` (Espanso 2.2.7) 3. `espanso start --unmanaged` 4. Remove Espanso from...