Qi Xiao
Qi Xiao
I filed an issue: https://gitlab.com/cznic/sqlite/-/issues/41 It's also unclear how mature the project is. In an issue from 4 months ago (https://gitlab.com/cznic/sqlite/-/issues/27) the author said that the priority is "completeness and...
Hmm, this will make one-off invocations of `read-line` more complex because they now need to deal with `$nil`. What's the scenario you're using `read-line` in where the current behavior is...
I like the `&eof` option idea.
Actually, I am wondering if there is a more general design. The `&eof` option only works when there is nothing to be read; it doesn't allow distinguishing when the remaining...
> The question is whether just "foo", without a trailing line ending at EOF, should return "foo" or throw the EOF exception. I'm inclined to think it should return "foo"...
OK, it was probably a bad idea to always warn about the existence of `~/.elvish`; I'll make the warning only appear when Elvish itself is actually using a file from...
As others said, there isn't any guidance at the moment yet.
A more radical change is to simply use function arguments:: ``` # Before for x [foo bar] { ... } for x [foo bar] { ... } # After for...
Another symptom of the same issue: doing `use edit` will make `edit:` an empty namespace.
I am mostly onboard with this idea. For the syntax, it could just be `x=foo`, letting the presense of a default value denote the optionality of the argument. However, the...