-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to build on latest #263
Comments
Ahh. That can be right, we don't do much with benchmarks. So it is probably obsolete code by now. Those benches can fixed is just a matter of changing some imports. |
I tried to fix this, but unfortunately, I've found that this isn't as easy as just tweaking some imports. The benches subcrate is treated as... just that, a subcrate, which means that it can't access any private interfaces. Apparently this has arisen as a problem for the bench in the past, there are notes like this in places: /// This is mimicking the `HeaderParser for AckedPacketHeader` implementation which is no longer
/// visible externally
As the crate has been added onto and reorganized, many more of the things that this bench is depending on have become private. Really, the bench is intended to test the speed of one simple internal interface. It tests how long it takes Laminar to process a packet. The benches crate can no longer access these functions though, because they've become private. I can think of two ways to fix this. Either I go and make the functions and types it relies on public, or I somehow move this benchmark somewhere inside the limits of the library, so that it has direct access to these interfaces. Which is preferable in the eyes of the Laminar developers and maintainers? |
Laminar supports sinds a few weeks a fake socket which uses in-memory transport instead of via UDP example of that can be found here. I think we can use that for those benchmarks. Secondly, we have the /bin folder, can't we use that for this somehow? I think it is better to rely on public interfaces. |
The text was updated successfully, but these errors were encountered: