like swift you say
> I do want to know what makes it so hard to get a platform from T2 to T1 Basically tier-1 targets must have tests run on CI for every merged commit. If anybody have a way to do that for their interest platforms, that's…
If the function you trying to keep is in non-pub module, it will be removed. Maybe you could move it out of private module: <https://rust.godbolt.org/z/PYPbG8>. There's also an `#[used]`[1] attribute, but only for…
> there is no feature in Rust to force a function to not be removed Can we use `pub` to make it public and not to be removed ?
So tell me if C/C++ or Kotlin do that.
Really! So now we have personal attacking shit instead of talking about technical info.
shellcheck.net/ is really nice to catch bugs in your bash scripts.
> nothing compile without nightly Have you ever compiled ripgrep?
Really nice. I hope GitHub use this option soon. Or maybe not: I guess it's kinda slow and heavy on computation.
We need more volunteers to help implement those features!
I am not serious. Often in these cases I would use printf debugging to know where the errors came. (I am still a Rust beginner).
Thanks through I still don't get it. I only know that you can get backtraces of errors by setting `RUST_BACKTRACE=1`.
What are the cases when `try!` macro bettern than `?` operator? I'm a beginner to Rust so I don't know about that.
like swift you say
> I do want to know what makes it so hard to get a platform from T2 to T1 Basically tier-1 targets must have tests run on CI for every merged commit. If anybody have a way to do that for their interest platforms, that's…
If the function you trying to keep is in non-pub module, it will be removed. Maybe you could move it out of private module: <https://rust.godbolt.org/z/PYPbG8>. There's also an `#[used]`[1] attribute, but only for…
> there is no feature in Rust to force a function to not be removed Can we use `pub` to make it public and not to be removed ?
So tell me if C/C++ or Kotlin do that.
Really! So now we have personal attacking shit instead of talking about technical info.
shellcheck.net/ is really nice to catch bugs in your bash scripts.
> nothing compile without nightly Have you ever compiled ripgrep?
Really nice. I hope GitHub use this option soon. Or maybe not: I guess it's kinda slow and heavy on computation.
We need more volunteers to help implement those features!
I am not serious. Often in these cases I would use printf debugging to know where the errors came. (I am still a Rust beginner).
Thanks through I still don't get it. I only know that you can get backtraces of errors by setting `RUST_BACKTRACE=1`.
What are the cases when `try!` macro bettern than `?` operator? I'm a beginner to Rust so I don't know about that.