Skip to content
New issue

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

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

Already on GitHub? # to your account

Name collisions with supporting types #39

Open
arg0d opened this issue Oct 11, 2023 · 1 comment
Open

Name collisions with supporting types #39

arg0d opened this issue Oct 11, 2023 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@arg0d
Copy link
Contributor

arg0d commented Oct 11, 2023

There are a bunch of supporting/internal types that can cause name collisions with consumer's namespace. These aren't very generic and not used very often unlike some other types, i.e. File, Stream, etc.., but thinking long term this could for sure create problems for someone. I wonder maybe its possible to neatly wrap all these supporting types into their own namespace.

AllocationException
BigEndianStream
CallStatusErrorHandler
ConcurrentHandleMap
FfiConverter*
FFIObject
FFIObjectUtil
FFISafeHandle
ForeignBytes
ForeignCallback
InternalException
InvalidEnumException
NullCallStatusErrorHandler
PanicException
RustBuffer
RustCallStatus
StreamUnderflowException
UndeclaredErrorException
UniffiException
@meenzen
Copy link
Contributor

meenzen commented Dec 28, 2023

In C# 11 it is possible to scope types to a specific file: https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/file

@arg0d arg0d added enhancement New feature or request bug Something isn't working labels Jan 18, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants