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
Towards Pencil 0.4 #49
Comments
PSA: I've published a fork called You can use it like:
and
There might be minor breakage with the updated dependencies (and possibly some type inference issues as I made the return values of MultiDics more flexible.) but nothing too drastic. |
👍 |
@fengsp What you think? |
Is this still being developed? |
I think that this project is essentially dead... There are other web frameworks in Rust that are more actively developed. |
Sharp Pencil 0.5 has been released after 3 and half years. |
It's essentially just a dependency bump, though :–D |
@golddranks It would be great if you could open issue tracker on your sharp_pencil fork, due to some changes in notify crate it no longer compiles. |
@micwoj92 Done! And let's see about the notify crate. |
Hi,
I've been using Pencil for the last few months, and I've built a web app that has now entering production stage. As I've been building my app, I've maintained a fork of Pencil, which has allowed me to quickly add features that I've needed. (The fork can be found here: https://github.com/golddranks/pencil/commits/master )
These changes include but are not limited to:
I also made some changes that may prove controversial:
I haven't really looked into how much work implementing more zero-copy parsing would be. Yet.
I'd like to contribute these changes back to Pencil, and help releasing Pencil 0.4. However, as the changes are just stop-gap solutions to my problems, I need to brush them up a bit if I were to contribute them. However, I want to have a confirmation from the maintainer @fengsp if he is willing to merge the PRs if I were to contribute stuff, since I don't want to do needless work :D What do you think?
The text was updated successfully, but these errors were encountered: