Re: Unchecked_Deallocation with tagged types

["Randy Brukardt" <randy@rrsoftware.com>]

"Vincent Marciante" <vincent.marciante@l3harris.com> wrote in message 
news:4205785c-6818-4e26-b931-5a775e2c426cn@googlegroups.com...
> On Tuesday, April 20, 2021 at 4:57:00 PM UTC-4, Jeffrey R. Carter wrote:
>> On 4/20/21 7:34 PM, Vincent Marciante wrote:
>> >
>> > Lists.List
>>
>> My objection is that this says the same thing twice (hence my joke about 
>> adding
>> more variants of "List" to it). "This is a list, and by the way, this is 
>> a
>> list." To me, Lists.Handle says, "This is something that lets you 
>> manipulate a
>> hidden implementation of lists."
>>
>> But the most important thing, I think, is that you've thought about 
>> naming ...
>
> But that idiom pretty much prohibits "using" more than one package with 
> such naming:

Yes, of course, that's a feature, not a bug. ;-)

One of the things that I learned when building Claw is that there is no 
naming convention that works well for use clauses and for the use-adverse. 
We ended up with a scheme that sort of works for both (using _Type) but it 
ideal for neither. I'd guess that most authors fall into one or the other 
camps and pick a scheme accordingly.

For me, a naming scheme that discourages the use of (package) use clauses is 
a bonus. (Such a scheme makes it easier to avoid use clauses.) I personally 
only use "use type" in new code (there's tons of old code for which that 
doesn't work, of course, but that doesn't change the principle).

                                    Randy.