4 Dec
2019
4 Dec
'19
3:03 p.m.
Gavin Lambert
With the [substr] method omitted, someone attempting a drop-in-replacement will get an error and will need to decide how best to handle it
This is fine if someone is changing code that just uses one string type, but it will break generic code that tries to work with all string types, unless you modify that generic code to require only the lowest common denominator. Telling users that they can't have a substr() method because they might use more stack space than they expected if their fixed_strings are large is a bit patronising towards the users, IMO. Regards, Phil.