Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Routing table lookup uses 4 ByteString splices where one might suffice #2

Open
rlupton20 opened this issue Jul 20, 2016 · 0 comments
Open

Routing table lookup uses 4 ByteString splices where one might suffice #2

rlupton20 opened this issue Jul 20, 2016 · 0 comments
Labels
enhancement investigation small

Comments

@rlupton20
Copy link
Owner

Can getDest, the worker function for routeWith (Routing/Routing.hs) uses 4 splices to build an IP address. Would a single splice and a fold be more efficient?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement investigation small
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rlupton20