std.range's put on arrays needs to change

[Basile B.]

On Saturday, 25 June 2022 at 23:44:59 UTC, WebFreak001 wrote:
> let's see this code:
> [...]
> I strongly feel that this behavior is very inconsistent and 
> unexpected for most users and should be changed.

I think nobody can disagree. A bit of archeology shows that's 
it's a very recurring topic:

- https://forum.dlang.org/post/pg5jso$s7o$1@digitalmars.com
- 
https://forum.dlang.org/thread/cewdrltvdrojojcxpwyr@forum.dlang.org
- 
https://forum.dlang.org/post/sckjdtlsccmfrmgjxpxg@forum.dlang.org
- 
https://forum.dlang.org/post/fhnfzlvhxzfxdebciacp@forum.dlang.org
- https://forum.dlang.org/post/ipg215$25e8$1@digitalmars.com
- https://forum.dlang.org/post/h5ensj$1880$1@digitalmars.com
- https://forum.dlang.org/thread/h5bdb8$2bcv$1@digitalmars.com
- https://issues.dlang.org/show_bug.cgi?id=14998
- https://issues.dlang.org/show_bug.cgi?id=3861

Deprecating the problematic behavior should not be a problem. 
Since on dynamic arrays `put()` does not do what people think it 
does, people dont use it.