Re:The ups of downs of porting 50k lines of C++ to Go
by z92 on Saturday March 07, 2015 @09:08AM
(#9161837)
Not without wasting a lot of space depending on the difference between average size of string vs maximum size of string.
[ Parent
| on HN ]
Re:The ups of downs of porting 50k lines of C++ to Go
by logicchains on Saturday March 07, 2015 @07:28PM
(#9163811)
We generally know the maximum string sizes for each property, and they're pretty small, so this wouldn't have been a problem.
Re:The ups of downs of porting 50k lines of C++ to Go
by a8da6b0c91d on Saturday March 07, 2015 @09:36AM
(#9161878)
You can use a string class like the one in Folly that decays from a fixed array to heap allocated space if the string gets too long.