I understand that, the cost of change is such that it's very unlikely
something like this ever goes into Python, but I feel like the interest of
the proposition is being underestimated here, that's why I'm going to argue
a few points and give a bit more context as needed.
> While mapping and filte
> If slice assignment is done as I hope it will optimize remain memory
operations.
Bad news.
http://stackoverflow.com/questions/4948293/python-slice-assignment-memory-usage/4948508#4948508
> If you want something like C++ move semantics, use C++.
I don't see anything like this in my proposal. I
2016-11-05 9:42 GMT+01:00 Steve D'Aprano :
>
> I don't know who you are quoting there. It is considered impolite to quote
> people without giving attribution, and makes it harder to respond.
>
My bad. I was unaware of that. This was quoted from Ned Batchelder's mali.
2016-11-05 9:42 GMT+01:00 S
2016-11-05 12:47 GMT+01:00 Chris Angelico :
> On Sat, Nov 5, 2016 at 9:50 PM, Arthur Havlicek
>
> But here's the thing. For everyone who writes a decorator function,
> there could be dozens who use it.
>
The day that one guy leaves the team, suddenly you have code that'
No escaping is not something possible, in your suggested syntax ") is
ambigous. E.g. raw("abcd")") is ambigous.
Any sequence delimited string involves escaping, the only thing that
wouldnt would be size-defined strings but they are impractical.
Le 20/04/2017 à 18:03, Mikhail V a écrit :
On 2
