oh, maybe they just trying random configuration (1min, 5min, or something
else)
and 2min is the best result
On Tuesday, December 14, 2021 at 4:13:05 PM UTC+7 Kurnia D Win wrote:
> okay, thanks for the explanation,
> suggesting me to change language to rust/c is not answering my curiosi
okay, thanks for the explanation,
suggesting me to change language to rust/c is not answering my curiosity
I ask it because I'm trying to learn the runtime, and the "why" behind some
decision that already made
for now, I will just follow it blindly, because the go developers already
made that de
will work fine, that is
why I'm curious what kind of trade-off we make here?
On Wednesday, December 8, 2021 at 9:32:39 AM UTC+7 kra...@skepticism.us
wrote:
> On Tue, Dec 7, 2021 at 6:20 PM Kurnia D Win wrote:
>
>> Why runtime force gc every 2 minute
Why runtime force gc every 2
minutes?,
https://github.com/golang/go/blob/016e6ebb4264f4b46e505bb404953cdb410f63f2/src/runtime/proc.go#L5226
AFAIK gc will be triggered when user try to allocate memory (the mallocgc
func)
and if user want to force gc every 2 minutes, they can create their own
g
Hi, I don't know if this kind of idea is already discussed before.
I have an idea of adding pure function marker/type on golang, it is just
like "constexpr" on C++ or "const fn" on Rust, whether this function is
evaluated at compile time if the input is known at compile time is another
discussi
