Don't count signature position changes inside string literals - #1738
Conversation
|
Ramya Rao (@ramya-rao-a) PTAL. I have to test it a bit more but it seems to fix the bug on the reported case of strings.Replace() |
|
PS: this also fixes an out of bounds access here |
|
Ramya Rao (@ramya-rao-a) After several adjustments I think it is ready to try, it works for most of the basic scenarios I came up with. All ci jobs failed with a seemingly unrelated npm error, so you'll have to trigger another build The following test fails locally but I see that it also fails on my local master branch, I'm not really sure why: |
|
I wasn't available this last month due to work but now I'm returning to my regular schedule Also, I couldn't find out the cause of this failure but it is a local issue only |
d711046 to
dfc1682
Compare
775752f to
490bb91
Compare
|
Luis Gabriel Gomez (@lggomez) I hope dont mind I refactored the existing code and reused the method you mentioned |
|
Not at all, this issue is long overdue so the fix will be really welcome into february's release 👍 |
Joel Hendrix (jhendrixMSFT)
left a comment
There was a problem hiding this comment.
Looks good and works as expected :)

Fixes #1682
I noticed (just after pushing my branch) that there already is an util function here that uses regexes. I didn't run any benchmarks comparing performance (assuming both methods work the same)