Open chuwy opened 11 months ago
Hi, these libraries are just prototypes. I'm planing on rewriting them as soon as possible, if you have any ideas on how to improve the code I would love to receive PRs or if you just start a new project I think I can just archive ash, melp and requests in favour of your project.
If you want to create an organization for it in order to organize all of these things, I would love to participate :)
If you want to create an organization for it in order to organize all of these things, I would love to participate :)
You said that! Let's try :) https://github.com/axiomed
Do you mind if I copy-paste some of your code then?
P.S. Feel free too to share ideas on naming, I'm not very good at it.
Do you mind if I copy-paste some of your code then?
Not a problem!
So lets organize this thing @chuwy. I saw that you created a repo called Http.lean
, It's going to be both the client and the server implementation? and the core that you mentioned? Can you create a repo for client, server and the core so we can just can make everything in parallel?
Hey @algebraic-sofia! Seems you're the first one to create a working HTTP ecosystem in Lean 4! Looks cool!
I'm wondering if you think it's a sane idea to collect all related stuff under one umbrella (let's assume it's going to be Melp), like it's done in http4s (Scala), where they have a single core (
http4s-core
), describing the whole domain of HTTP primitives like methods, statuses, requests, responses etc, thenhttp4s-client
(that is yourrequests
) to operate those entities to make requests andhttp4s-server
to accept those requests (moremelp
rather thanash
).Asking because I'm trying to write a Servant analog in lean4 and looking for unified description of HTTP domain and there's bit of duplication between
requests
andmelp
. Obviously not critical now, but trying to imagine what future might look like.I can send a PR if you think it would work out for you.