public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
To: "馬 冰" <bingmatv@outlook.com>,
	"Adhemerval Zanella" <adhemerval.zanella@linaro.org>
Cc: "rms@gnu.org" <rms@gnu.org>,
	"libc-help@sourceware.org" <libc-help@sourceware.org>,
	"help-bash@gnu.org" <help-bash@gnu.org>
Subject: Re: Richard M. Stallman says GNU/Linux, but Rust lang ecosystem is growing.
Date: Thu, 11 Apr 2024 15:12:39 +0300	[thread overview]
Message-ID: <6dbc66feec4a383213cf2bdcc1b3bc2b4cba3948.camel@yandex.ru> (raw)
In-Reply-To: <MW3PR22MB22847FE8D67A887D2D67C0ECD0052@MW3PR22MB2284.namprd22.prod.outlook.com>

On Thu, 2024-04-11 at 12:05 +0000, 馬 冰 wrote:
> 
> "it's just an adapter from internal API to one operating on `int`s,
> i.e.
> `Ok()` will be converted to `0`, and an error will be converted to
> another number", it may cost more memory if using 2 type systems
> simultaneously. Rust Result can use Box to allocate errors with
> unknown size on heap, whereas int is fixed-size, they may be
> incompatible due to unknown size and fixed-size.

Are you seriously motivated enough to start rewriting POSIX and other
standards and convincing people to break backward compatibility just to
save 8 bytes? Well… good luck

      reply	other threads:[~2024-04-11 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 12:43 bingmatv
2024-03-31 14:04 ` Adhemerval Zanella
2024-03-31 14:50   ` tomas
2024-04-02  1:44     ` Dennis Clarke
2024-04-07  7:27   ` 馬 冰
2024-04-07  7:45     ` Konstantin Kharlamov
2024-04-11 12:05       ` 馬 冰
2024-04-11 12:12         ` Konstantin Kharlamov [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=6dbc66feec4a383213cf2bdcc1b3bc2b4cba3948.camel@yandex.ru \
    --to=hi-angel@yandex.ru \
    --cc=adhemerval.zanella@linaro.org \
    --cc=bingmatv@outlook.com \
    --cc=help-bash@gnu.org \
    --cc=libc-help@sourceware.org \
    --cc=rms@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).