From: Noam Preil <noam@pixelhero.dev>
To: 9front@9front.org
Subject: Re: [9front] Re: commit 2f8a59f4b5bfe028c022855acc19666d69eed909
Date: Wed, 1 Sep 2021 19:16:20 +0000 (UTC) [thread overview]
Message-ID: <533fabd0-bf67-484a-8ec8-d6d91d0e9d4f@pixelhero.dev> (raw)
In-Reply-To: <C07BF59C797BF35114F03583FCC85B76@eigenstate.org>
Given that fn foo{@{}} already works I think this patch is unnecessary even without getting into whether function coloring is a good idea.
prev parent reply other threads:[~2021-09-01 19:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 7:48 Anthony Martin
2021-07-09 14:21 ` ori
2021-07-09 14:37 ` Stanley Lieber
2021-07-09 14:56 ` ori
2021-07-09 15:01 ` ori
2021-07-09 15:10 ` Stanley Lieber
2021-07-09 19:43 ` hiro
2021-07-09 20:44 ` hiro
2021-07-09 20:50 ` Stanley Lieber
2021-07-10 7:25 ` hiro
2021-07-10 14:16 ` Stanley Lieber
2021-08-27 15:07 ` ori
2021-09-01 19:16 ` Noam Preil [this message]
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=533fabd0-bf67-484a-8ec8-d6d91d0e9d4f@pixelhero.dev \
--to=noam@pixelhero.dev \
--cc=9front@9front.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).