I think it is a misinterpretation that this topic goes away with Python3. Both
Python2 and Python3 provide *two* string types. Hence, having a second string
type in IronPython would certainly help Python2 compatibility as well as
Python3 compatibility.
I don't agree with your statement about .
Hi, Pawel,
I’m not that deep into the inner workings of IronPython string handling, my
impression until now was that we just used the .NET Strings 1:1, using clever
binding for the members.
For your approach, I think we we’d need our own wrapper instance around the
.NET String objects, so the
As usual, I agree with you Pawel :)
That said, I don't have a lot of "handcrafted tweaks for str/unicode
aliasing", so it's easy for me to dismiss that negative.
To me, your proposal sounds elegant, but I am open to consensus.
--Tim
On Sat, Sep 17, 2016 at 3:13 AM, Pawel Jasinski
wrote:
> hi,
