proc-macro-workshop
Giraffe
proc-macro-workshop | Giraffe | |
---|---|---|
26 | 19 | |
3,816 | 2,055 | |
- | 0.8% | |
4.3 | 6.8 | |
26 days ago | 24 days ago | |
Rust | F# | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proc-macro-workshop
-
Why does the core not provide a "New" derive attribute?
Tangentially, the proc macro workshop walks through building a derive macro implementing a builder pattern. From experience, I can tell I couldn't ever write proc macros just by reading the manual, going through it is really helpful https://github.com/dtolnay/proc-macro-workshop/blob/master/README.md
-
Help on spans for proc macros
I am working on the proc macro workshop and am a little stuck on the builder portion of the workshop. Step 08-unrecognized-attributes wants you to handle the car where the field modifier has a misspelled portion (eac instead of each)
-
Practical Procedural Macros in Rust
I would very much second the suggestion to do David Tolnay’s Proc Macro Workshop if you want to start understanding how to write them. I’d been writing Rust for years but always kind of avoided proc macros.
When I had a need for them, I went through only the first section of the workshop and everything clicked. You can just do the derive macro section and all the strange and scary-looking macro syntax will make sense. I realized that there is only a bit of extra syntax but it’s used very often so it can seem a little overwhelming when reading macro code.
https://github.com/dtolnay/proc-macro-workshop
- Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
-
A walkthough on how to write derive procedural macros
Another good one imo is the proc-macro-workshop.
-
Transitioning to Rust as a company
Don't be afraid of proc macros and derive macros, they rule. Study the basic examples. Crates like darling and resources like David Tolnay's workshop will help. Write derives for your simpler traits and impress your colleagues.
-
What are your experiences with hack-and-learn events?
Regarding 4, I think that macros are an interesting intermediate/advanced topic. I personally loved the material from https://github.com/dtolnay/proc-macro-workshop
-
Procedural Macros are really hard to understand
It took me a while to get anything done. My mistake : I came accross the procedural macros workshop several times, and every time I dismissed it, thinking - meh I'll just hack together exactly what I need and move on. Then finally I figured there is no way around it. The builder exercise sounds boring but it covers the topic pretty well. And then I went on to the debug one and from there was able to build the proc macro I wanted.
-
MacroKata is really good!
Hey! While researching, I found this: https://github.com/dtolnay/proc-macro-workshop
-
Anything C can do Rust can do Better
Rust Latam: procedural macros workshop - David Tolnay
Giraffe
-
The combined power of F# and C#
Giraffe is another interesting one to explore: https://giraffe.wiki/
Giraffe is nice because it is itself built "just" as ASP.NET Core Middleware so it plays a bit more nicely than Suave with a mixed stack of C#-defined Middleware.
It's more likely you accidentally fall back into just translating C# patterns to non-idiomatic F# with Giraffe, but it's also nicer when in that case of needing to live in both worlds and use a mixture of libraries built for C# ASP.NET projects.
-
ASP.NET Core updates in .NET 8 Preview 4 - .NET Blog
There are also some F# frameworks built on top of ASP.NET core like https://giraffe.wiki
- Confusion in learning Giraffe's HttpHandler
-
Is there any advantage to using F# instead of C#?
If you have an interest in F#, I highly recommend diving in because (1) it has a ton of things you might learn to appreciate in C#; (2) it has things C# cannot have. I do like some of the suggestions people have made regarding mixing your code bases, but I'll also say that building, say, endpoint routing in Giraffe is (to repeat myself) easy, simple, and elegant.
-
Targeting Node, Bun and Deno With F#
Bix is a micro-framework designed with F# in mind and that runs on both Deno and Bun! and in theory it also should even run in a service worker! (intercepting fetch requests) although I haven't tested that yet, it offers a general purpose handler that coupled with a set of route definitions it can bring a Giraffe/Saturn like framework to life in JavaScript runtimes which is incredibly awesome! useful? maybe not 😅, but awesome indeed. Let's see some code for it
-
If you were to create a Web API today from scratch how would you do it ?
Backend: Most likely it would be a toss between https://saturnframework.org or https://giraffe.wiki. They both combins the extremely good type system in F# combined with the ease of a minimal API.
-
Is it possible to run C# asp.net core MVC and f# giraffe in a single solution
I was wondering if its possible to simultaneously run a C# core MVC project in combination with https://github.com/giraffe-fsharp/Giraffe
-
Overriding JSON serializer in Giraffe
By default Giraffe, the framework which I use as a web server, uses Newtonsoft.Json to serialize results to JSON. However, for discriminated union, it generates quite a lot of JSON so I've switched to System.Text.Json which is built into newer versions of .Net Core. In combination with FSharp.SystemTextJson package allows serializing discriminated unions more gracefully. All we need is to decorate Branch type with JsonFSharpConverter(JsonUnionEncoding.BareFieldlessTags) attribute.
-
Introducing Giraffe.Htmx
Giraffe is a library that sits atop ASP.NET Core and allows developers to build web applications in a functional style; dotnet new giraffe is literally my starting point when I begin a new web application project. (Rather than write three more sentences filled with effusive praise, I’ll just leave it at that; it’s great.) It also provides a view engine (that builds upon Suave‘s “experimental” view engine) which uses an F# DSL to define HTML in a strongly-typed way. It has been incredibly efficient for a while, but with .NET’s work over the past two releases at improving performance, and Giraffe’s adoption of those techniques, it is lightning fast.
-
Show HN: F# web server in 3-4 lines of code
Wrapping ASP.NET Core to be easier and more idiomatic with F# seems to be a common domain. Out of curiosity, did you look at any existing projects? If so, what was lacking from them that made you decide to write WebFrame?
Giraffe: https://github.com/giraffe-fsharp/Giraffe
What are some alternatives?
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
Suave.IO - Suave is a simple web development F# library providing a lightweight web server and a set of combinators to manipulate route flow and task composition.
cargo-expand - Subcommand to show result of macro expansion
Saturn - Opinionated, web development framework for F# which implements the server-side, functional MVC pattern
rust-learnings - Collection of Rust learnings through implementation
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
style - css for rust
Falco - A toolkit for building fast and functional-first web applications using F#.
quote - Rust quasi-quoting
ASP.NET MVC
style - Style Dart Backend Framework
Freya - Freya Web Stack - Meta-Package