Date: Sun, 23 Aug 2026 14:52:52 +0200
> > To be clear, I'm not suggesting a big_int type for C, only the limb type
> that could be used internally.
> >
> > The C version of the feature would likely end up looking like a
> stdc-prefixed version of GNU MP, and I'm not really sure how much benefit
> there is to standardizing that, or whether WG14 has any appetite for
> copying and pasting GMP into the C standard.
>
> I think C should have a native bigint type. I suggested
> this before (not in a paper).
>
Just so we're on the same page: what do you mean by "native"?
Do you mean a builtin bigint type with "constructors" and "destructors"
that calls malloc and free upon initialization and when it goes out of
scope?
Or do you just mean some bigint struct that lives in the C standard library?
> that could be used internally.
> >
> > The C version of the feature would likely end up looking like a
> stdc-prefixed version of GNU MP, and I'm not really sure how much benefit
> there is to standardizing that, or whether WG14 has any appetite for
> copying and pasting GMP into the C standard.
>
> I think C should have a native bigint type. I suggested
> this before (not in a paper).
>
Just so we're on the same page: what do you mean by "native"?
Do you mean a builtin bigint type with "constructors" and "destructors"
that calls malloc and free upon initialization and when it goes out of
scope?
Or do you just mean some bigint struct that lives in the C standard library?
Received on 2026-08-23 12:53:10
