Alexander Plavin

should be a tiny change, any issues with it?..

Sorry, forgot about this for a while! > triage approves. > @aplavin add a news entry and we can merge. Added.

I think the only reasonable way to define `setindex` semantics is to follow `setindex!` as closely as possible. Anything else would be very confusing. AFAICT, this is the case with...

Note that `setindex` is not some obscure function, it's used and sometimes overloaded [in many](https://juliahub.com/ui/Search?type=code&q=(using|import)+Base:+.*setindex(,|$)&rx=true) [packages](https://juliahub.com/ui/Search?type=code&q=Base.setindex[^!]&rx=true). I don't really have more arguments for making it public than - it's a...

Semiannual bump

> but this would be a breaking change Before 1.11 release is the only time to make such "breaking" changes (not really breaking because feature wasn't released). Otherwise Julia and...

> It also makes annotations a bit more of a pain to write if you're writing a lot of them The constructor can support both annotations formats: one convenient for...

> Mmm, so I'd say the contenders for the form are: IMO anything with reasonable names is better than opaque numbers, don't have a preference between 2 and 3. >...

I was even a bit surprised this went into Base without trying out the interface in a package first... https://github.com/JuliaLang/julia/pull/49586#issuecomment-1704076289 But now – nice if at least readily apparent and...

> hm, we don't have as much control over this. Is there some fundamental issue with converting it to an empty BezierPath, without any drawing commands? > it would be...