Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.3.2 #32

Merged
merged 7 commits into from
Aug 29, 2024
Merged

0.3.2 #32

merged 7 commits into from
Aug 29, 2024

Conversation

BenWoodworth
Copy link
Owner

No description provided.

Previously, comparing KProperties from delegates would either work
completely (jvm/native), or not at all (js), so a quick runtime check
was enough to determine whether KProperty.equals could be used. But now
the Wasm targets only sometimes work, and other times don't, depending
on the property and how it's declared, which resulted in some usages
failing. To properly solve this, the `KProperty.equalsProperty` function
was made into an `expect` function, and each platform actualizes it
according to whether `KProperty.equals` works or not.
> The following actions use a deprecated Node.js version and will be
> forced to run on node20: actions/checkout@v3, actions/setup-java@v3.
> For more info:
> https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
@BenWoodworth BenWoodworth merged commit 197bfeb into main Aug 29, 2024
8 checks passed
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.

1 participant