Closed nordlow closed 2 years ago
doesn't using std.experimental.*
potentially introduce breaking changes without warnings?
It would probably make sense to update the stdx-allocator package to contain the new std.experimental.allocator code
Potentially, yes, but with deprecation warnings as usual if they are breaking. The only potential deprecations in std.experimental.allocator I can think of would be changes to allocator member function qualifiers. The problem with having libdparse use stdx.allocator is that it contaminates dsymbol and dscanner to also use instances of stdx.allocators as stdx-specific allocators are passed as IAllocator
-parameters to constructors of some of the libdparse classes that are inherited in dsymbol. A leaky abstraction that is.
FYI, @RazvanN7.
+1 for removing the stdx dependency.
To avoid silent regression, libdparse should be added to the dlang community tester (if it is not already on that list).
So, shall I do the switch?
https://github.com/dlang-community/stdx-allocator hasn't been modified for 2 years.
Should libdparse, dsymbol and dscanner move to the more recently updated
std.experimental.allocator
?If there's a consensus I can do the migration.
FYI, @RazvanN7