David Anthoff
David Anthoff
And now it continues in https://github.com/JuliaLang/juliaup/pull/1095.
Bump, I would also be interested in a status update on this for the Julia extension :)
@DonJayamanne so I think in general the more the better, at the end of the day any package might just assume that things are run in a terminal that supports...
@DonJayamanne and @amunger just wanted to check in on this again, this is probably the number one pain point I have right now with the notebook stuff for Julia :)...
I looked a bit more, and I think if we could fix https://github.com/julia-vscode/julia-vscode/issues/3561 it would already be great progress. @DonJayamanne or @amunger if you could point me in the right...
I think another consideration here is consistency: the other functions we have that take an individual element from an iterator are `first` and `last`, and both throw an error if...
> We could also opt for relying on the `IteratorEltype` trait I have to admit, I think that is the option I like least of all of the proposed options...
> `nth` and `trynth` seems a bit more julian than a `nothrow` kwarg Yes, agreed! Having two distinct functions probably also helps with type stability. Another naming scheme I thought...
The idea really is that there are no test items (nor `include`s) in `runtests.jl`, just the macro call to run the tests, so that one doesn't need to load TestItems.jl....
There was a bug in the VS Code extension runner where it didn't pick up your local env. I just fixed that in the prerelease of VS Code. I'm not...