ocaml-lsp
ocaml
ocaml-lsp | ocaml | |
---|---|---|
9 | 119 | |
715 | 5,162 | |
0.7% | 0.7% | |
7.7 | 9.9 | |
8 days ago | 3 days ago | |
OCaml | OCaml | |
GNU General Public License v3.0 or later | 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.
ocaml-lsp
-
I Wrote an Activitypub Server in OCaml: Lessons Learnt, Weekends Lost
> There is no alternative to Django, for instance.
https://aantron.github.io/dream/, which is new and used by ocaml.org
> No serious IDE, except emacs
and vim, and visual studio, and whatever else supports the LSP protocol via https://github.com/ocaml/ocaml-lsp
> The standard library was so lacking that there is at least an alternative.
While janestreet does have an publish their own stdlib, I personally try to stick to the stdlib whenever possible. Not to knock janestreet. I'm glad they're around and have contributed a bunch.
But overall I agree with you. It's been my favorite language two write in for years now. You can't just reach for off-the-shelf libraries for every little thing. Although the ones that do exist tend to be written halfway decently.
-
Merlin: Context sensitive completion for OCaml in Vim and Emacs
Merlin is great, but it's vim plugin leaves a bit to be desired (in particular, it doesn't seem to use any of the modern async apis from vim 8+/neovim). Personally ocaml-lsp (which is still backed by Merlin on the backend) together with neovim's built-in lsp support has been far smoother for me
-
The New OCaml Website
Perhaps the README[1] is out of date, but it appears to note that textDocument/implementation is not done? That's a pretty big hole.
[1]: https://github.com/ocaml/ocaml-lsp/#features
- Neovim 0.7 Released
-
Toplevel in VSCode?
Short answer: yesWith https://marketplace.visualstudio.com/items?itemName=ocamllabs.ocaml-platformand https://github.com/ocaml/ocaml-lspand https://dune.readthedocs.io/en/stable/and utop
-
This week in KDE: Fixing a bunch of annoying bugs
This is the one I tried and seems well supported - https://github.com/ocaml/ocaml-lsp . I've only started very lightly playing around with ocaml. It seems to be working fine on vscode and seems to do as expected on nvim too, at least as far as I configured nvim for it.
-
opam install problem on Ubuntu 21.04
Typically I would recommend using https://github.com/ocaml/ocaml-lsp which is now the main OCaml language server, and VSCode with the OCaml Platform extension, a combo I know works well.
-
In the Interest of Building an SML Language Server
You might also look into ocaml-lsp for inspiration. Not everything will carry over to SML but it might help somtimes.
ocaml
-
Autoconf makes me think we stopped evolving too soon
> OCaml’s configure script is also “normal”
If that’s this OCaml, it has a configure.ac file in the root directory, which looks suspicious for an Autotools-free package: https://github.com/ocaml/ocaml
-
The Return of the Frame Pointers
You probably already know, but with OCaml 5 the only way to get flamegraphs working is to either:
* use framepointers [1]
* use LBR (but LBR has a limited depth, and may not work on on all CPUs, I'm assuming due to bugs in perf)
* implement some deep changes in how perf works to handle the 2 stacks in OCaml (I don't even know if this would be possible), or write/adapt some eBPF code to do it
OCaml 5 has a separate stack for OCaml code and C code, and although GDB can link them based on DWARF info, perf DWARF call-graphs cannot (https://github.com/ocaml/ocaml/issues/12563#issuecomment-193...)
If you need more evidence to keep it enabled in future releases, you can use OCaml 5 as an example (unfortunately there aren't many OCaml applications, so that may not carry too much weight on its own).
[1]: I haven't actually realised that Fedora39 has already enabled FP by default, nice! (I still do most of my day-to-day profiling on an ~CentOS 7 system with 'perf --call-graph dwarf', I was aware that there was a discussion to enable FP by default, but haven't noticed it has actually been done already)
-
Top Paying Programming Technologies 2024
11. OCaml - $91,026
-
OCaml: a Rust developer's first impressions
> It partially helps since it forces you to have types where they matters most: exported functions
But the problém the OP has is not knowing the types when reading the source (in the .ml file).
> How would it feels like to use list if only https://github.com/ocaml/ocaml/blob/trunk/stdlib/list.ml was available,
If the signature where in the source file (which you can do in OCaml too), there would be no problem - which is what all the other (for some definition of "other") languages except C and C++ (even Fortran) do.
No, really, I can't see a single advantage of separate .mli files at all. The real problém is that the documentation is often worse too, as the .mli is autogenerated and documented afterwards - and now changes made later in the sources need to be documented in the mli too, so anything that doesn't change the type often gets lost. The same happens in C and C++ with header files.
-
Bringing more sweetness to ruby with sorbet types 🍦
If you have been in the Ruby community for the past couple of years, it's possible that you're not a super fan of types or that this concept never passed through your mind, and that's totally cool. I myself love the dynamic and meta-programming nature of Ruby, and honestly, by the time of this article's writing, we aren't on the level of OCaml for type checking and inference, but still, there are a couple of nice things that types with sorbet bring to the table:
-
What is gained and lost with 63-bit integers? (2014)
Looks like there have been proposals to eliminate use of 3 operand lea in OCaml code (not accepted sadly):
https://github.com/ocaml/ocaml/pull/8531
-
Notes about the ongoing Perl logo discussion
An amazing example is Ocaml lang logo / mascot. It might be useful to talk with them to know what was the process behind this work. The About page camel head on Perl dot org header is also a pretty good example of simplification, but it's not a logo, just a friendly illustration, as the O'Reilly camel is. Another notable logo for this animal is the well known tobacco industry company, but don't get me started on that (“good” logo, though, if we look at the effectiveness of their marketing).
-
What can Category Theory do?
Haskell and Agda are probably the most obvious examples. Ocaml too, but it is much older, so its type system is not as categorical. There is also Idris, which is not as well-known but is very cool.
- Playing Atari Games in OCaml
-
Bloat
That does sound problematic, but without the code it is hard to tell what is the issue. Typically, compiling a 6kLoc file like https://github.com/ocaml/ocaml/blob/trunk/typing/typecore.ml takes 0.8 s on my machine.
What are some alternatives?
neovimcraft - website that makes it easy to find neovim plugins
Alpaca-API - The Alpaca API is a developer interface for trading operations and market data reception through the Alpaca platform.
merlin - Context sensitive completion for OCaml in Vim and Emacs
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
nvim-completion - :zap: An async autocompletion framework for Neovim
dune - A composable build system for OCaml.
which-key.nvim - 💥 Create key bindings that stick. WhichKey is a lua plugin for Neovim 0.5 that displays a popup with possible keybindings of the command you started typing.
TradeAlgo - Stock trading algorithm written in Python for TD Ameritrade.
neovim - Vim-fork focused on extensibility and usability
melange - A mixture of tooling combined to produce JavaScript from OCaml & Reason
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
rust - Rust for the xtensa architecture. Built in targets for the ESP32 and ESP8266