Paul Backus

@schveiguy Made it a wrapper.

Is it really a problem to check for the `--version` option *after* parsing instead? E.g., ```d void main(string[] args) { import std.getopt; bool showVersion; // ... auto result = args.getopt(...

Might be worth submitting a draft PR that just changes `OpenRight.no` to include the full sentinel, and see if any of the projects tested on Buildkite break. If we can...

> What about a use case where you want to use the GC as a standard allocator, but get the benefits of having the memory scanned because it's in the...

> What about making `GCAllocator.deallocate` a no-op method which always returns `true`? I think that would be most meaningful. A no-op `deallocate` method does not free any memory, so having...

> The definition [of `GCAllocator`] is an implementation of a `std.allocator` allocator backed by memory managed by the D GC. I don't see why the fact that the allocated memory...

> By itself it seems at odds with the general description of `std.allocator` allocators, which aim to facilitate manual memory management, right? My understanding is that `std.allocator`'s allocators are supposed...

> So it comes back to, if the question is "can this allocator deallocate?", and the answer is "yes, but it's not going to happen right away", how to represent...

> It's also not how DbI is used for other methods. Granted, but I'm not talking about other methods, I'm talking about `deallocate`. And a container *must* call `deallocate` if...

> A shim layer is the conceptually correct solution here, because it makes a statement of information that would otherwise need to be transmitted downwards across layers (this would mean...