You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The spec just says that all IDs are numbers - which is to say, 64-bit floats. It does not say much about how they should be compared, including weird cases like NaN or positive/negative zero, which are seemingly legal.
In practice it seems that protocol clients have much more stringent limitations - for example, VS uses 32-bit integers internally for many IDs, and is unable to cope with any number that doesn't fit. It would be nice to reflect it in the spec itself, limiting the values to some sane subset that all current implementations support in practice (e.g. int32 > 0?).
The text was updated successfully, but these errors were encountered:
DAP schema types all IDs as integers, so, clearly, they cannot be fractional numbers. Since VSCode is implemented in javascript, I think the largest integer it can handle is 253 - 1.
The spec just says that all IDs are
number
s - which is to say, 64-bit floats. It does not say much about how they should be compared, including weird cases likeNaN
or positive/negative zero, which are seemingly legal.In practice it seems that protocol clients have much more stringent limitations - for example, VS uses 32-bit integers internally for many IDs, and is unable to cope with any number that doesn't fit. It would be nice to reflect it in the spec itself, limiting the values to some sane subset that all current implementations support in practice (e.g.
int32 > 0
?).The text was updated successfully, but these errors were encountered: