From: "Carlos Maniero" <carlos@maniero.me>
To: "Johnny Richard" <johnny@johnnyrichard.com>
Cc: <~johnnyrichard/olang-devel@lists.sr.ht>
Subject: Re: [PATCH olang v1 1/2] docs: spec: rename program to translation-unit
Date: Thu, 28 Mar 2024 10:50:14 -0300 [thread overview]
Message-ID: <D05FJR3X0FS5.3B581X4AGUWZR@maniero.me> (raw)
In-Reply-To: <34zmjbgj3m6wbmwccjp3prnf3l76jwbpdati5hi3xep35cka2c@lhcwkygn5jfl>
> > commit also makes a few refactors on spec such as:
> >
> > - Makes EOF a end-of-statement
>
> This patch does the opposite. Make a end-of-statement a EOF as well,
> which I not agree. See following comments...
>
...
>
> Hmmm... this is not true, this means the every end-of-statement can be a
> end-of-file.
I'll try a different approach and send a new patch, the challenge here
is that you should not be able to do that:
fn a(): u32 {} fn b(): u32 {}
fn a(): u32 {} var a: u32 fn b(): u32 {}
That's was the issue I was trying to address when I make EOF a EOS. To
allow multiple definitions that requires an new line in between.
next prev parent reply other threads:[~2024-03-28 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 3:21 [PATCH olang v1 0/2] docs: variables specification Carlos Maniero
2024-03-27 3:21 ` [PATCH olang v1 1/2] docs: spec: rename program to translation-unit Carlos Maniero
2024-03-27 21:20 ` Johnny Richard
2024-03-28 13:50 ` Carlos Maniero [this message]
2024-03-27 3:21 ` [PATCH olang v1 2/2] docs: spec: add variables and constants specification Carlos Maniero
2024-03-27 3:22 ` [olang/patches/.build.yml] build failed builds.sr.ht
2024-03-27 21:37 ` [PATCH olang v1 2/2] docs: spec: add variables and constants specification Johnny Richard
2024-03-28 14:11 ` Carlos Maniero
2024-04-01 17:48 ` Johnny Richard
2024-03-30 1:14 ` Carlos Maniero
2024-04-01 17:54 ` Johnny Richard
2024-04-11 22:39 ` [PATCH] fixup! " ricardo_kagawa
2024-04-12 22:36 ` Johnny Richard
2024-04-13 2:18 ` Carlos Maniero
2024-04-16 19:01 ` Johnny Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D05FJR3X0FS5.3B581X4AGUWZR@maniero.me \
--to=carlos@maniero.me \
--cc=johnny@johnnyrichard.com \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox