search for: setxyz

...s can safely be added to the API. Around 40 have already been added to WRE with API annotations; another 40 or so can probably be added after review. The remainder mostly fall into two groups: - Entry points that should never be used in packages, such as SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that matter) that can create inconsistent or corrupt internal state. - Entry points that depend on the existence of internal structure that might be subject to change, such as the existence of promise objects or internal structure of environments. Many, if not most, of thes...

...Around 40 have > already been added to WRE with API annotations; another 40 or so can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that > matter) that can create inconsistent or corrupt internal state. > > - Entry points that depend on the existence of internal structure that > might be subject to change, such as the existence of promise objects > or internal structure of environments. &gt...

...Around 40 have > already been added to WRE with API annotations; another 40 or so can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that > matter) that can create inconsistent or corrupt internal state. > > - Entry points that depend on the existence of internal structure that > might be subject to change, such as the existence of promise objects > or internal structure of environments. &gt...

...Around 40 have > already been added to WRE with API annotations; another 40 or so can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for that > matter) that can create inconsistent or corrupt internal state. > > - Entry points that depend on the existence of internal structure that > might be subject to change, such as the existence of promise objects > or internal structure of environments. &gt...

...dded to WRE with API annotations; another 40 or so > can > probably be added after review. > > The remainder mostly fall into two groups: > > - Entry points that should never be used in packages, such as > ? ?SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for > that > ? ?matter) that can create inconsistent or corrupt internal > state. > > - Entry points that depend on the existence of internal > structure that > ? ?might be subject to change, such as the existence of promise >...

...nother 40 or so > > can > > probably be added after review. > > > > The remainder mostly fall into two groups: > > > > - Entry points that should never be used in packages, such as > > SET_OBJECT or SETLENGTH (or any non-API SETXYZ functions for > > that > > matter) that can create inconsistent or corrupt internal > > state. > > > > - Entry points that depend on the existence of internal > > structure that > > might be subject to change, such...