Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Tim Rentsch <tr.17687@z991.linuxsc.com> |
|---|---|
| Newsgroups | comp.std.c |
| Subject | Re: request for feedback: n2698 - generic functions and parametric types |
| Date | 2023-01-29 10:57 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <86y1plf9tr.fsf@linuxsc.com> (permalink) |
| References | <04f0a483-554c-40d2-bf79-4c5155a0ebban@googlegroups.com> <865ydpq6o2.fsf@linuxsc.com> <422b8eb9-f6b0-403d-af65-c433aec47a9dn@googlegroups.com> |
"Leandro T. C. Melo" <ltcmelo@gmail.com> writes: > On Monday, January 2, 2023 at 12:48:17 PM UTC-3, Tim Rentsch wrote: > >> This proposal is painfully bad, along a variety of axes. >> Perhaps the most important axes are that it isn't clear exactly >> what is being proposed, > > The proposal (draft) describes, with examples, how a programmer > writes generic functions/parametric types and how a compiler > translates them in stages; what's left unclear in your opinion? > >> and to the extent that what is being >> proposed is evident it looks like it is not very well thought >> out. > > Could you justify this claim? > >> The constructs described look like they are more or less a >> trimmed-down version of C++ templates, > > Why do you think so? > The constructs involved in the proposal, along with the instantiation > mechanism?which isn't based on template argument deduction > rule/two-phase name lookup?, aren't borrowed from C++. > In terms of the expressivity of the design, it's sort of a > "trimmed-down version" of C++ templates, just as it's a trimmed-down > version of generics in C#/Java/Go, typeclasses in Haskell, etc. > >> but with an even worse >> syntax than templates (and I can't tell what differences there >> might be in the semantics, in areas where the two overlap). > > If you don't like the syntax, fine... but there shouldn't be a single > overlap in the semantics; could you point out to me what you refer > to? > >> Also the writing and presentation are awful, which really doesn't >> help. > > Again, without a justification (e.g., in terms of > writing/presentation criteria), your statement doesn't have any > credibility. > >> I am sympathetic to the idea that C might benefit from having >> some kind of template or parameterized type mechanism, but what >> is suggested in this proposal is not it. > > What a cliche. > >> Specific comment: don't use the word "generic". C already has a >> construct that could be called "generic", namely _Generic. > > _Generic is addressed in the proposal; where the use of the word > "generic" is intentional (and explained). Your earlier posting said "I'd appreciate any feedback a lot", and feedback is what I gave. Were you actually looking for someone to have an argument with? I don't see any appreciation expressed in your comments.
Back to comp.std.c | Previous | Next — Previous in thread | Next in thread | Find similar
request for feedback: n2698 - generic functions and parametric types "Leandro T. C. Melo" <ltcmelo@gmail.com> - 2022-11-29 04:31 -0800
Re: request for feedback: n2698 - generic functions and parametric types Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-01-02 07:48 -0800
Re: request for feedback: n2698 - generic functions and parametric types "Leandro T. C. Melo" <ltcmelo@gmail.com> - 2023-01-03 03:32 -0800
Re: request for feedback: n2698 - generic functions and parametric types Tim Rentsch <tr.17687@z991.linuxsc.com> - 2023-01-29 10:57 -0800
Re: request for feedback: n2698 - generic functions and parametric types "Leandro T. C. Melo" <ltcmelo@gmail.com> - 2023-01-29 14:35 -0800
csiph-web