Skip to content

Conversation

@LaurentRDC
Copy link
Member

This is a work-in-progress of a Cloud Haskell backend based on QUIC

Fixes #474

@LaurentRDC LaurentRDC force-pushed the network-transport-quic branch 5 times, most recently from b0f9529 to e990e98 Compare August 19, 2025 00:02
@LaurentRDC LaurentRDC force-pushed the network-transport-quic branch 2 times, most recently from a0e3c03 to 5e159a4 Compare August 28, 2025 17:47
@LaurentRDC LaurentRDC force-pushed the network-transport-quic branch 4 times, most recently from f5b2aac to 08a8a99 Compare September 9, 2025 01:04
@LaurentRDC LaurentRDC force-pushed the network-transport-quic branch from 08a8a99 to 71c103e Compare October 5, 2025 23:35
@LaurentRDC
Copy link
Member Author

Getting this done is incredibly hard. I can't believe how hard it is to spin up a new transport layer.

One thing that makes it harder than it should is that some behavior is only documented via tests. So I got 80% of the way to the tests passing, but the next set of tests require a whole lot of refactoring.

I don't think I'll have the time (or motivation) to get back to this in the near future. At least I found and fixed a bug in the underlying quic library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Creating a transport layer based on QUIC

1 participant