Fixed string concat to cstring conversion #427
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
would incorrectly output
"01"
, at least in my local machine which at that time happened to allocate a zeroed out memory chunk on anlpvm alloc
. This problem is more noticeable when calling!logmsg(<log_str>)
, as<log_str>
is first converted into a cstring.The culprit seems to be the
incr(!offset)
line. The line is unnecessary asoffset
has been incremented accordingly in each recursivepack
call.wybe/wybelibs/wybe/string.wybe
Lines 180 to 183 in 35b5c14
Perhaps unrelated to the main problem, but I have also changed the third argument of
mutate
tolen - 1
, which I believe is more accurate, although I have yet to see a corner case for this.wybe/wybelibs/wybe/string.wybe
Lines 40 to 49 in 35b5c14