Add changelog entry about ndslice removal#4967
Conversation
| The synchronization between Phobos and Mir turned out to be a lot of work | ||
| with litte gain. Users of `std.experimental.ndslice` are advised to | ||
| switch to the upstream $(LINK2 https://github.com/libmir/mir-std, | ||
| mir package). |
There was a problem hiding this comment.
@9il I used the same link as you proposed in the deprecation warning.
There was a problem hiding this comment.
It was changed to mir-algorithm. I don't think I understand now what we should put into mir-std, probably this would be only traits and meta and maybe compiler intrinsics.
changelog.dd
Outdated
| deprecated.) | ||
| The synchronization between Phobos and Mir turned out to be a lot of work | ||
| with litte gain. Users of `std.experimental.ndslice` are advised to | ||
| switch to the upstream $(LINK2 https://github.com/libmir/mir-std, |
| The synchronization between Phobos and Mir turned out to be a lot of work | ||
| with litte gain. Users of `std.experimental.ndslice` are advised to | ||
| switch to the upstream $(LINK2 https://github.com/libmir/mir-std, | ||
| mir package). |
|
Thank you for the PR! |
wilzbach
force-pushed
the
ndslice-removal-changelog
branch
from
1828122 to
0968df4
Compare
Argh - sorry for the copy/paste error :/ |
|
FYI: @MartinNowak and I are still testing a new |
Thanks for doing this! |
Hm..., not sure of the state of this, but I prefer the auto-merge system actually posting the message that auto merge has been toggled on, because that goes to my inbox. I also prefer the merge being done with the credentials of the person who toggled auto-merge. Is that possible with the way you do it? |
|
UI-wise, I like the idea of having the merge toggle in github. But I'm a bit concerned about accidentally merging because you clicked the wrong label. Definitely there needs to be a delay in merging (probably at least 20 seconds). |
General remark: as said we are just testing things and possible solutions, so this won't be set in stone. However your feedback is very welcome and I do encourage everyone to open issues.
This would be very easy to do. I opened an issue to discuss it as there might be people how don't want this, but they could just setup a filter or block the bot directly.
Me too, but we don't want to store your credentials with write access in the cloud, hence we use
You could also accidentally hit the "green" merge button - it would be immediate as well. |
That's not next to the "allocator" label button 😉 |
|
Hm... a crude idea on that -- the labels seem listed alphabetically, you could make the label "ZZZ auto-merge" so they are always at the bottom. |
That lessens the concern quite a bit! |
4 participants
Follow-up to #4946
CC @9il