-
Notifications
You must be signed in to change notification settings - Fork 9
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
Current Planning 2022-07 #105
Comments
Right now I'm looking at the ownership model with Johan (in parallel but we will sync at some point), and the shared library support, as I believe it's mandatory to help with integrating in lilbmamba. |
Shared library support is done: #112 |
We use |
That point is more about correctness and ease of reasoning (so that correctness can be "read") than performance, which is why "value semantics" is often pushed a lot against any kind of pointer and reference semantics. |
I will list here the issues I have noted to work on and discussed with @wolfv and @JohanMabille, priorities are mostly on integration into mamba and correctness. Most of these issues imply reviews, discovery and discussion.
Important for helping with integration in Mamba:
libpowerloader
as shared library support: currently missing explicit symbol import/export markers for correct generation of dlls on windows and potentially constraint the ABI surface and binary size of shared libraries on other platforms.libmamba
andlibpowerloader
, there are several ways to do this and it's possible it is not worth it for now.libpowerloader
: if issues with unicode are possible, we might need to use Use standard C++ filesystem API only mamba#1665 inlibpowerloader
too.Code Quality Improvements:
Note: I named this issue quickly, not sure if that's a good name.
Powerloader integration in mamba: mamba-org/mamba#1503
The text was updated successfully, but these errors were encountered: