Squid
klister
Our great sponsors
Squid | klister | |
---|---|---|
1 | 7 | |
197 | 122 | |
0.5% | - | |
0.0 | 5.6 | |
about 2 months ago | 9 days ago | |
Scala | Haskell | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
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.
Squid
-
Haskell doesn't have macros
In the video, the presenter says he doesn't know any other system with "type-aware hygienic macros". You may want to have a quick look at Scala 3, which also has such a system. See, for instance, this paper and also the precursor work by myself for Scala 2: https://github.com/epfldata/squid#publications
klister
-
Interactive animations
Yeah, that project is pretty much at the bottom of my list, unfortunately. My top projects these days are mgmt, klister, recursion-schemes, and hint... And that's already too much!
-
Rust Tests Itself (Kind of!)
case is a special form, ie a bit of core syntax, but, interestingly, data is not. (It is presumably a macro; typechecking is actually done as a part of macro expansion.) The syntax remains pretty uniform. Or, in Klister, type ascription is done via normal S-expression syntax with a form called the, as (the $type $expression); again, the syntax is uniform.
-
How do you typecheck a macro?
You might be interested in Klister: https://github.com/gelisam/klister
-
Using defmacro's &environment argument to implement Racket's hygienic macro expansion system?
I've now also found an implementation for klister, which is meant to interleave type checking with macro expansion.
-
Haskell doesn't have macros
In Klister, which already has Scheme-like macros and Haskell-like types (polymorphism, algebraic types and higher-kinded types, but not yet fancier types like RankNTypes and GADTs), our plan to get the best of both worlds (lexical syntax and typed ASTs) is to separate parsing from macro evaluation. That is, users write their programs using the surface syntax of s-expressions, parsers parse those into typed ASTs, and macros are typed by the type of the ASTs they receive as input and produce as output. At this stage this is only a research idea, I don't know if that's going to work out yet, but I hope so!
What are some alternatives?
Monocle - Optics library for Scala
Cassovary - Cassovary is a simple big graph processing library for the JVM
refined - Refinement types for Scala
Twitter Util - Wonderful reusable code from Twitter
n-scala - A new Scala wrapper for Joda Time based on scala-time
scribe - The fastest logging library in the world. Built from scratch in Scala and programmatically configurable.
Each - A macro library that converts native imperative syntax to scalaz's monadic expressions
rakudo - 🦋 Rakudo – Raku on MoarVM, JVM, and JS
Scala-Logging - Convenient and performant logging library for Scala wrapping SLF4J.
better-files - Simple, safe and intuitive Scala I/O
Scalaz - Principled Functional Programming in Scala
Quicklens - Modify deeply nested case class fields