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

Memory management model and language features #312

Closed
ghost opened this issue Feb 16, 2024 · 2 comments
Closed

Memory management model and language features #312

ghost opened this issue Feb 16, 2024 · 2 comments

Comments

@ghost
Copy link

ghost commented Feb 16, 2024

I know the memory management model is an integral part of the runtime, so language features will depend on it. But to what extent? I don't know, since Adept also supports manual memory management. For example, if you change the memory management model in the future and I restrict myself to pure C-style manual memory management, then which language features will be available to me, and will my code work in the new Adept?

@IsaacShelton
Copy link
Collaborator

Adept 3.x is still in the design phase, but yes it is planned to break backwards-compatibility.

It will effectively be a new language.

They will probably not be interoperable.

Adept 2.x will always be supported though.

So I wouldn't worry about trying to make your code future-proof with 3.x. If it really concerns you, you can always make a static library in Adept 2.x, as I can guarantee that 3.x will support static libraries.

Adept 2.x will still always be supported of course.

@IsaacShelton
Copy link
Collaborator

Also there may be migration tools, although we will see

This issue was closed.
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

No branches or pull requests

1 participant