Skip to content

Conversation

bnoordhuis
Copy link
Contributor

JSValueConst was only used for the now removed CONFIG_CHECK_JSVALUE build mode. It is kept around as an alias for JSValue in quickjs.h to avoid breaking everyone's source builds but remove it everywhere else.


If you're wondering if this was a perl -i -pe 's/JSValueConst/JSValue/g' oneliner - yes :)

JSValueConst was only used for the now removed CONFIG_CHECK_JSVALUE
build mode. It is kept around as an alias for JSValue in quickjs.h to
avoid breaking everyone's source builds but remove it everywhere else.
@bnoordhuis bnoordhuis merged commit f1b7b6d into quickjs-ng:master Dec 10, 2023
@bnoordhuis bnoordhuis deleted the rm-jsvalueconst branch December 10, 2023 14:15
saghul added a commit that referenced this pull request Dec 19, 2023
@saghul saghul mentioned this pull request Dec 19, 2023
saghul added a commit that referenced this pull request Dec 20, 2023
@forworldm
Copy link

Removing JSValueConst discards ownership semantics. JSValue takes ownership while JSValueConst not.

@saghul
Copy link
Contributor

saghul commented Dec 25, 2023

In normal builds it was equivalent.

Or are you talking about the implied semantics?

bluesky950520 pushed a commit to bluesky950520/quickjs that referenced this pull request Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants