Anton Korobeynikov

@fruffy abseil contains `absl::BitGen` / `absl::InsecureBitGen`. Maybe worth exploring as a replacement for `boost::random` See https://abseil.io/docs/cpp/guides/random and https://abseil.io/about/design/random

I tend to agree with @vlstill as it seems to be some bad interaction with standard library. Anyway, if boost uses things that were deprecated in C++17 and removed in...

> What about [fmt](https://github.com/fmtlib/fmt)? Will also be much easier to replace with `std::format` in the future. it is nice, yes. But probably we'd need to check / benchmark different solutions

> Hmm, I think at least for the usage of boost::format in the compiler most of the calls are used for debugging/warnings/errors, which are not that performance-critical, no? Going with...

@jafingerhut Some time ago we implemented bounded loops downstream. They employ `for (variable in sequence)` syntax as a way to enforce that the loop is indeed bounded (it seems quite...

Sure, I can see what could be done.

> I added an extra commit with the IR changes for this. I've almost finished porting our changes for the loops. I will post a PR shortly

I ported our downstream code at https://github.com/p4lang/p4c/pull/4558 Currently use-def changes are missed, I am working on porting them asap. Let me know if there are any questions / comments /...

I was not part of the original discussion, so do not know about all the details here. But my understanding is that if the intention is to support bounded loops,...

> Yes, p4test does not have any non-core dependencies (except the control-plane maybe). We could make it optional too but then we only have `gtest`. I would probably vote to...