The obligatory permalink and latest draft.
The only difference is new subsections of § Maximal Munch Exceptions.
Thread overview | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
September 24 Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
The obligatory permalink and latest draft. The only difference is new subsections of § Maximal Munch Exceptions. |
September 26 Re: Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
Posted in reply to Quirin Schroll | On Tuesday, 24 September 2024 at 20:50:58 UTC, Quirin Schroll wrote: >The obligatory permalink and latest draft. The only difference is new subsections of § Maximal Munch Exceptions. The new sections look good. Currently the spec only mentions maximal munch for the lexer and not the parser. The typo |
September 26 Re: Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
Posted in reply to Tim | On Thursday, 26 September 2024 at 18:05:51 UTC, Tim wrote: >On Tuesday, 24 September 2024 at 20:50:58 UTC, Quirin Schroll wrote: >The obligatory permalink and latest draft. The only difference is new subsections of § Maximal Munch Exceptions. The new sections look good. Currently the spec only mentions maximal munch for the lexer and not the parser. The typo I just don’t understand how we live in 2024 and Visual Studio has no working spellcheck on Markdown. The proper spelling and some other wording issues are resolved now. |
October 04 Re: Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
Posted in reply to Quirin Schroll | On Tuesday, 24 September 2024 at 20:50:58 UTC, Quirin Schroll wrote: >The obligatory permalink and latest draft. The only difference is new subsections of § Maximal Munch Exceptions. A question, probably out of ignorance: Why do function pointers / delegates need to care about their linkage type? I thought that a function pointer can freely point to any function that is otherwise of the correct type, regardless of it's linkage type. Is this not the case? |
October 05 Re: Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
Posted in reply to Dukc | On 05/10/2024 12:13 AM, Dukc wrote:
> On Tuesday, 24 September 2024 at 20:50:58 UTC, Quirin Schroll wrote:
>> The obligatory [permalink](https://github.com/Bolpat/DIPs/blob/fcb076e4be19abf634bcadbb7567c49ed80c084c/DIPs/DIP-2NNN-QFS.md) and [latest draft](https://github.com/Bolpat/DIPs/blob/PrimaryTypeSyntax/DIPs/DIP-2NNN-QFS.md).
>>
>> The only difference is new subsections of [§ Maximal Munch Exceptions](https://github.com/Bolpat/DIPs/blob/fcb076e4be19abf634bcadbb7567c49ed80c084c/DIPs/DIP-2NNN-QFS.md#maximal-munch-exceptions).
>
> A question, probably out of ignorance: Why do function pointers / delegates need to care about their linkage type?
>
> I thought that a function pointer can freely point to any function that is otherwise of the correct type, regardless of it's linkage type. Is this not the case?
No.
Linkage affects both mangling and the ABI (how it is called).
Parameters and return values could be in different locations if it was mixed up.
|
October 07 Re: Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
Posted in reply to Richard (Rikki) Andrew Cattermole | On Friday, 4 October 2024 at 22:24:15 UTC, Richard (Rikki) Andrew Cattermole wrote: >No. Linkage affects both mangling and the ABI (how it is called). Parameters and return values could be in different locations if it was mixed up. I see, thanks. In that case it's good that the DIP addresses it. In general I like a lot about this DIP is proposing but I should do a deeper dive. Maybe I will but not today. |
October 19 Re: Fourth Draft: Primary Type Syntax | ||||
---|---|---|---|---|
| ||||
Posted in reply to Quirin Schroll | Time for another dive. I still generally like this proposal. But I did gather However, unless misleading spaces are inserted between the type qualifier and the opening parenthesis, this exception follows mathematical conventions and programmers’ intuition This left me confused for quite a while. The exception to parsing rules that I did figure out you meant that the meaning of linkage In declarations, linkage works mostly like attributes (both user-defined and There's one potential weakness in my idea though: it assumes that non-function Regardless, probably anonymous classes Example? I maybe know what you're writing about and proposing here but it's hard to be sure. Maybe while there, you could also propose a syntax for function types without |