Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Safer encode/decode variant. #27485
This PR supersedes the other three. Closes #27399 Closes #27398 Closes #27442 .
It also add docs for thos functions, but breaks ABI compatibaility (API compatibility for GDNative).
The question on what to do when cherry picking is left to release maintainers (@hpvb @akien-mga)... Should we only cherry-pick the first 3 (actively disabling a dangerous behaviour some users may rely on), or cherry pick all 5 commits, breaking ABI, still changing API behaviour for those dangerous cases, but giving users a chance to still decode objects by adding a parameter to their function call?
Please bear with me, helping out double-checking that changes are correct.
EDIT: Note that there is also a compat braking change where