Skip to content

☂ Publish core without AccessOverloadApi annotated functions by default and additional core-compact artifact #1156

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

Open
koperagen opened this issue Apr 28, 2025 · 2 comments
Assignees
Labels
infrastructure GitHub actions, Gradle Scripts, Writerside, etc. ☂ umbrella issue Label assigned to issues that are collections of smaller issues
Milestone

Comments

@koperagen
Copy link
Collaborator

No description provided.

@koperagen
Copy link
Collaborator Author

Some of these could be somewhat blocked because proper replacement would require compiler plugin to be available in project / notebook. But i recommend to just remove / replace with String API whenever possible, and discuss when in doubts

@Jolanrensen Jolanrensen added the ☂ umbrella issue Label assigned to issues that are collections of smaller issues label May 28, 2025
@Jolanrensen Jolanrensen changed the title Publish core without AccessOverloadApi annotated functions by default and additional core-compact artifact ☂ Publish core without AccessOverloadApi annotated functions by default and additional core-compact artifact May 28, 2025
@Jolanrensen
Copy link
Collaborator

Some of these could be somewhat blocked because proper replacement would require compiler plugin to be available in project / notebook. But i recommend to just remove / replace with String API whenever possible, and discuss when in doubts

During KotlinConf and my demos/the workshop I indeed noticed a lot of deprecations now appear in notebooks. It's not ideal to have the safest possible path be deprecated while we're waiting for the compiler plugin.

As for our DataFrame project itself, I'd advise not adding the compiler plugin. The bootstrapping of the Gradle plugin has caused many issues (and it's still causing issues atm). Instead, we can generate extensions we need manually or rely on strings indeed :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure GitHub actions, Gradle Scripts, Writerside, etc. ☂ umbrella issue Label assigned to issues that are collections of smaller issues
Projects
None yet
Development

No branches or pull requests

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy