Name-QuickSearch
unison
| Name-QuickSearch | unison | |
|---|---|---|
| 1 | 17 | |
| 4 | 5,564 | |
| - | 1.0% | |
| 0.0 | 9.9 | |
| over 2 years ago | 2 days ago | |
| Haskell | Haskell | |
| MIT License | GNU General Public License v3.0 or later |
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.
Name-QuickSearch
-
QuickSearch, a tool for comparing sets of names [newbie]
Hey all, this is my first serious attempt at making something in Haskell and I'd really appreciate any feedback you might have, be it whether something is not idiomatic Haskell or if there's a simpler/better way to accomplish something. https://github.com/osoleve/Name-QuickSearch
unison
- Unison Programming Language
-
Unison Cloud
Short version: no type classes (yet)
Longer version:
Building upon what Quekid5 mentioned, Unison abilities are an implementation of what is referred to as algebraic effects in programming language literature. They represent capabilities like IO, state, exceptions, etc. They aren't really a replacement for type classes, though in some cases you can shoehorn abilities in where you might otherwise use a type class.
For someone coming from a Haskell background, I think that abilities are closer to a replacement for monad transformers. But in my opinion they are much more ergonomic.
Discusson of type classes comes up a lot. Here is a long-standing GitHub issue: https://github.com/unisonweb/unison/issues/502
For what it's worth, I've written Unison quite a lot over the past few years and while I've missed type classes at times, I think that reading unfamiliar code is easier without them. There's no implicit magic; you can see exactly what is being passed into a function. So far I've been happy with a bit more verbosity for the sake of readability.
-
Show HN: Winglang – a new Cloud-Oriented programming language
I've been following the Unison lang [1] for quite some. Wing seem to set similar goals? From the first glance Wing looks more polished, but there's "The Big Idea" behind Unison - is there something similar?
[1]: https://github.com/unisonweb/unison
- Unison Language
-
C++ evolution vs C++ successor languages. Circle's feature pragmas let you select your own "evolver language."
in haskell it looks like this, you specify the language extensions you want at the top of the source files: https://github.com/unisonweb/unison/blob/trunk/unison-core/src/Unison/ABT.hs
-
Looking for a new language to learn for Advent of Code that's unlike anything you've tried before? Check out Unison!
they adjusted my ticket to be a bug fix on their part.
-
Syntax Design
I think Unison is going in this direction. Imo this is a mistake, as a program language functions not just as specification for the machine, but also as communication between programmers. Allowing the introduction of arbitrary dialects to suit individual preferences seems like it would interfere with that communication.
- Unison
- Unison Milestone 3
- What if Git worked with Programming Languages?
What are some alternatives?
nvim-treesitter-context - Show code context
dark - Darklang main repo, including language, backend, and infra
project-m36 - Project: M36 Relational Algebra Engine
cone - Cone Programming Language
nbdime - Tools for diffing and merging of Jupyter notebooks.
structured-haskell-mode - Structured editing minor mode for Haskell in Emacs
UwUpp - The next generation esoteric language
structured-haskell-m
syntactic_versioning - What if Git worked with Programming Languages?
lawvere - A categorical programming language with effects
git-merge-driver - Example of how to configure a custom git merge driver
diffsitter - A tree-sitter based AST difftool to get meaningful semantic diffs