Carlo Baldassi

One way in which zeroing out bits could be subtly problematic, IIUC, is this: say you have some code which does `Array{SomeType}(3)`, where `SomeType` is immutable and comes from a...

It's not fixed unfortunately. Here's a miminal example to reproduce, that mimics my use case. Save this into a file "jtst.jl": ```julia module JTst using FileIO, ArgParse function getx() fn...

As far as I can tell, that should be pretty easy to do, almost straightforward. The "not installed" condition is treated by the resolver like one possible version (the highest-priority...

Sorry for the long hiatus. @IanButterworth that code would try to call `pvers[p1][spp[p1]]` which is out of bounds, see https://github.com/JuliaLang/Pkg.jl/blob/91b4e05b57b146c78fcd066c2e1942735b9a6ddc/src/Resolve/graphtype.jl#L128-L129 Re-reading the thread, I think had likely misunderstood the original...

Sorry Ian, I've been really strapped for time lately (family reasons, mostly). I am hoping to work on this during this weekend.

Sure, I'll look into it as soon as I can

No, but it's rather easy to implement it without much extra typing compared to a built-in version: ```julia using ArgParse function main(args) s = ArgParseSettings("Example of choice") choices = ["1/3",...

It's not exactly intended behavior. I wouldn't know how to call them though. This is one of the reasons why I disliked this feature. By the way, this is also...

Sorry for being so late in looking into this, it slipped under my radar for quite a while. I don't fully understand the use case though. It seems to me...

I see. Maybe a more general feature would be to have an internal list associated to a special key (`"%PARSED_ARGS%"`, for example) that lists what options were passed? I think...