semantic-source
tig
semantic-source | tig | |
---|---|---|
23 | 59 | |
8,862 | 12,161 | |
0.2% | - | |
9.1 | 7.3 | |
about 1 month ago | 8 days ago | |
Haskell | C | |
MIT License | GNU General Public License v3.0 only |
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.
semantic-source
-
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.
[1] https://github.com/github/semantic
[2] https://github.com/github/semantic/pull/535
-
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/
tig
-
Every Git Command I Use (Cheatsheet)
Related but I use tig, a TUI, a lot to examine the state of my working tree and index and stage/unstage/reset changes piecemeal. It works great.
- Tig: Text-Mode Interface for Git
-
Magit
I'd like to plug [tig](https://github.com/jonas/tig) for those who don't use emacs. I see lazygit recommended here too, but I've been using tig for years now and love it's simplicity.
-
Is there any solution like Github Desktop and Gitkraken For terminal Users
Try tig
-
What is your preferred version control software and what additional features do you wish it had?
I'm normally a CLI git (and tig) user.
-
TexStudio - git integration for easy committing?
Sometimes when I work in command line I use tig (https://jonas.github.io/tig/). There is also similar tool lazygit (https://github.com/jesseduffield/lazygit)
-
gti, gtti, giit, gut, gti, got, hit, jit, git <enter> {f%ck} <up-arrow-key>
And you accidently open a git TUI
-
This is how I use vim and git, any other tips?
tig +My custom command to fix MR comments by quickly editing an old commit's changes at the time when that commit was created. (Like a more controlled git-absorb that explicitly selects a commit to fixup and therefor avoids rebase-conflicts when squashing)
-
tig to switch branches
today I looked at tig which is a nice text based GUI, and I think I will never use git log again :-)
-
interactive git switch
If you are looking for more interactivity while remaining on the commandline, have you looked at Tig? Tig has a view for browsing refs, and you can sort by date.
What are some alternatives?
diffsitter - A tree-sitter based AST difftool to get meaningful semantic diffs
lazygit - simple terminal UI for git commands
massiv - Efficient Haskell Arrays featuring Parallel computation
gitui - Blazing 💥 fast terminal-ui for git written in rust 🦀
refined - Refinement types with static checking
lazygit.nvim - Plugin for calling lazygit from within neovim.
cantor-pairing - Convert data to and from a natural number representation
vim-floaterm - :computer: Terminal manager for (neo)vim
jump - Jump start your Haskell development
gitsigns.nvim - Git integration for buffers
Glean - System for collecting, deriving and working with facts about source code.
cz-cli - The commitizen command line utility. #BlackLivesMatter