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

D std::map bindings using the wrapper method #22

Open
wants to merge 17 commits into
base: v1.x.x
Choose a base branch
from

Conversation

Emmankoko
Copy link
Collaborator

@Emmankoko Emmankoko commented May 17, 2024

The wrapper method was decided to be used for std::map because macOS symbol generation with template instantiations is largely inconsistent and affects the stability of the module on CppRuntimeClang.

This is an initial show of the complete setup of how it will be distributed as a package. more symbols will be added but I want the initial work to be very clear for easy review.

add opIndexAssign test
private static fileds are mangled as C and public static fields are mangled as S on MSVC. since fields with no access modifeiers in C++ classes are private by default, it affects the mangling of the fields on windows so need for public there
also fields that are private on the D side should match on C++ side. Posix doesn't really care about those but msvc does.

match private with private for msvc
@Emmankoko Emmankoko force-pushed the map branch 2 times, most recently from 1824ea1 to 4eb9cac Compare June 7, 2024 13:19
@Geod24
Copy link
Member

Geod24 commented Jun 18, 2024

I see what this is doing, and it would work great in a project trying to use std::map, but it does not work great as a binding.
If we can't force emit those symbols, look like we have to bite the bullet and reimplement it in D.

@Emmankoko
Copy link
Collaborator Author

I see what this is doing, and it would work great in a project trying to use std::map, but it does not work great as a binding. If we can't force emit those symbols, look like we have to bite the bullet and reimplement it in D.

haha true. I'll handle that

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.

2 participants