From: "Carlos Maniero" <carlos@maniero.me>
To: "Johnny Richard" <johnny@johnnyrichard.com>
Cc: <~johnnyrichard/olang-devel@lists.sr.ht>
Subject: Re: [RFC SPEC] Primitive data types and arrays
Date: Fri, 12 Apr 2024 23:51:51 -0300 [thread overview]
Message-ID: <D0INKDECJMDD.3EPYTTM3HJZNO@maniero.me> (raw)
In-Reply-To: <luc74cmsdjrtcmpnthz2oaqpwkrpxfilgzn3mdmplcr237o3ix@ihmktgnrpy4x>
> I loved it. Out of curiosity, we are going to have _boolean_ and _char_
> I believe. Shouldn't they also be included on these primitive spec?
I like it! We could discuss in the near feature if they are or not just
type alias for u8. But I also agree they must be built-in without the
need of any include.
<primitive-type> ::= 's8'| 's16'| 's32'| 's64'| 'u8'|
'u16'| 'u32'| 'u64'| 'f32'| 'f64'|
'char' | 'bool'
<expression> ::= <integer> | <identifier> | <boolean> | <char>
<boolean> ::= "true" | "false"
<char> ::= "'" #'.' "'"
Are you comfortable with the above grammar?
> Sure. I like it. I think we can split this RFC up into different RFCs.
> One for discuss primitive types and another one for discussing arrays in
> general. What do you think?
LGTM! Let's conclude this one first and them I start a new thread.
next prev parent reply other threads:[~2024-04-13 2:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 3:29 Carlos Maniero
2024-04-12 7:32 ` Johnny Richard
2024-04-13 2:51 ` Carlos Maniero [this message]
2024-04-13 23:31 ` Johnny Richard
2024-04-16 3:40 ` Carlos Maniero
2024-04-16 18:34 ` Johnny Richard
2024-04-17 1:30 ` ricardo_kagawa
2024-04-18 21:53 ` Carlos Maniero
2024-04-24 16:23 ` ricardo_kagawa
2024-04-20 11:45 ` Johnny Richard
2024-04-24 18:45 ` ricardo_kagawa
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=D0INKDECJMDD.3EPYTTM3HJZNO@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