sequential-index
[Haskell] Sequential index numbers between 0.0 and 1.0 that allow arbitrarily inserting new numbers in between (for special containers). (by aristidb)
semantic-source
Parsing, analyzing, and comparing source code across many languages (by github)
Our great sponsors
| sequential-index | semantic-source | |
|---|---|---|
| - | 23 | |
| 2 | 8,858 | |
| - | 0.3% | |
| 0.0 | 9.1 | |
| about 11 years ago | 25 days ago | |
| Haskell | Haskell | |
| BSD 3-clause "New" or "Revised" License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
sequential-index
Posts with mentions or reviews of sequential-index.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning sequential-index yet.
Tracking mentions began in Dec 2020.
semantic-source
Posts with mentions or reviews of semantic-source.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-13.
-
The Meaning of Monad in MonadTrans
One production example I know: GitHub code navigation is written in Haskell https://github.com/github/semantic
- Semantic: Parsing, analyzing, and comparing source code across many languages
-
How to Get Started with Tree-Sitter
ah, easy. it's because support has not been added into https://github.com/github/semantic which is the tech that powers the GitHub UI. Adding support is pretty easy/mainly glue code [1] that imports the tree sitter API.
[1] https://github.com/github/semantic/blob/793a876ae45d38a6bd17...
- Scala community now has control over the official Scala grammar for tree-sitter 🎉
- 2022 State of Haskell Survey
-
11 Companies That Use Haskell in Production
GitHub used Haskell for implementing Semantic, a command-line tool for parsing, analyzing, and comparing source code.
-
What happened with GitHub's semantic project?
As far as engineering effort, you can read this GitHub comment for an overview of where we’d like to take the project in the future. The tl;dr here is that the open sum type view of the world made it very concise to fold over syntax trees (since such a view of data is ultimately unityped, recursion schemes Just Work), but the tradeoff thus associated—namely, that you have to parse a concrete syntax tree into an open-sum view (a complicated and painful-to-read process), that you can never really be sure how a given syntax tree is shaped, and that the types don’t help you nearly as much as they could—proved to be too onerous to deal with. Going forward, we’re generating syntax types from the AST once per target language, and working on an abstraction (probably via this generated code; I made five separate efforts at using Generics for this, and failed every time) that recovers at least some of the convenience of recursion schemes. It turns out that recursion schemes over a mutually recursive syntax tree—as pretty much every language’s syntax trees are, in practice—are pretty much an unsolved problem, especially when extended to languages like TypeScript, which have hundreds of different syntax nodes.
-
Stack Graphs
Meanwhile their Tree-Sitter-based semantic parser[1] looks abandoned. There is even rotting for years pull request[2] adding support of the same stack graphs into it.
-
Cardano relying on Haskell is not bad at all
The semantic team at GitHub uses it for statically analyzing the dozens of languages that end up in GitHub repositories: https://github.com/github/semantic/blob/eaf13783838861fe5eb6cd46d59354774a8eb88d/docs/why-haskell.md
-
7 Useful Tools Written in Haskell
Yesterday I was looking for some examples of projects using tree-sitter (which is C) when I found GitHub's semantic, used to analyze and compare source code, and written in Haskell: https://github.com/github/semantic/
What are some alternatives?
When comparing sequential-index and semantic-source you can also consider the following projects:
primitive - This package provides various primitive memory-related operations.
diffsitter - A tree-sitter based AST difftool to get meaningful semantic diffs
json-autotype - Automatic Haskell type inference from JSON input
massiv - Efficient Haskell Arrays featuring Parallel computation
tables - Deprecated because of
cantor-pairing - Convert data to and from a natural number representation
certificate - Certificate and Key Reader/Writer in haskell
refined - Refinement types with static checking
reflection - Reifies arbitrary Haskell terms into types that can be reflected back into terms
jump - Jump start your Haskell development
text-icu - This package provides the Haskell Data.Text.ICU library, for performing complex manipulation of Unicode text.
Glean - System for collecting, deriving and working with facts about source code.
sequential-index vs primitive
semantic-source vs diffsitter
sequential-index vs json-autotype
semantic-source vs massiv
sequential-index vs tables
semantic-source vs cantor-pairing
sequential-index vs certificate
semantic-source vs refined
sequential-index vs reflection
semantic-source vs jump
sequential-index vs text-icu
semantic-source vs Glean