clangd | rfcs | |
---|---|---|
53 | 666 | |
1,323 | 5,711 | |
3.7% | 0.8% | |
1.8 | 9.8 | |
11 days ago | about 8 hours ago | |
Shell | Markdown | |
Apache License 2.0 | Apache License 2.0 |
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.
clangd
-
Speeding up C++ build times
I'm still waiting for clangd support, e.g. [0] before trying modules.
- [0] https://github.com/clangd/clangd/issues/1293
-
Configure clangd in eglot to not add headers?
I know one way to do this, but hoping there's something simpler or more general. clangd (C++ LSP server) is over-aggressive about adding "helpful" #includes during completion. The way to turn that off is to pass -header-insertion=never on its cmd line.
-
A little help for a C++ newbie
Install the clangd language server using your system package manager, e.g. sudo apt-get install clangd
-
Effect of Perceptual Load on Performance Within IDE in People with ADHD Symptoms
> As a side note, I despise things like imports and aliases. I'd prefer that when I do jump to a function, I can read it without having to check if anything is imported or not.
One idea might be to use an LSP (Language Server Protocol) interface. It could describe the fully qualified symbol for you when you, say, select the abbreviated symbol or press a keyboard shortcut. I've been working on a moderately large C program with Emacs and clangd[1] recently and have been amazed at how 'immersive' it feels, and that's from someone who's used to the comfort of a Lisp REPL!
[1]: https://clangd.llvm.org/
-
#include Cleanup Available in Visual Studio 2022 17.7 Preview 3
FWIW, recent clangd also has this feature: "unused" as of 14, "missing" as of 16, works better in snapshots.
-
How to set up C++ in sublime text?
You need to install CMake (and use it to build your project - which you should do in any case) and clangd.
-
Guide for starting out C and C++ Programming in Visual Studio Code
First we would need the Clangd extension as well as the LSP itself You can download the extension from #here The extension provides its own Clangd LSP but in case of issues with that we would like to download and setup the clangd package from the official site for both Windows and Linux I daily drive Linux on my laptop, thus this guide works well for linux users, Windows users can use programs like Cygwin to replicate the process
-
Does C/C++ OpenMP pragmas break clangd LSP for you?
Few days ago I found a bug while using clangd LSP with neovim, and submitted a bug report to clangd: https://github.com/clangd/clangd/issues/1640
-
vscode alternative for C++ on M1 mac?
Come to the light side: VSCodium with clangd
-
Looking for projects to contribute to
If you use the clangd LSP: https://github.com/clangd/clangd/issues
rfcs
-
Ask HN: What April Fools jokes have you noticed this year?
RFC: Add large language models to Rust
https://github.com/rust-lang/rfcs/pull/3603
- Rust to add large language models to the standard library
-
Why does Rust choose not to provide `for` comprehensions?
Man, SO and family has really gone downhill. That top answer is absolutely terrible. In fact, if you care, you can literally look at the RFC discussion here to see the actual debate: https://github.com/rust-lang/rfcs/pull/582
Basically, `for x in y` is kind of redundant, already sorta-kinda supported by itertools, and there's also a ton of macros that sorta-kinda do it already. It would just be language bloat at this point.
Literally has nothing to do with memory management.
- Coroutines in C
-
Uv: Python Packaging in Rust
Congrats!
> Similarly, uv does not yet generate a platform-agnostic lockfile. This matches pip-tools, but differs from Poetry and PDM, making uv a better fit for projects built around the pip and pip-tools workflows.
Do you expect to make the higher level workflow independent of requirements.txt / support a platform-agnostic lockfile? Being attached to Rye makes me think "no".
Without being platform agnostic, to me this is dead-on-arrival and unable to meet the "Cargo for Python" aim.
> uv supports alternate resolution strategies. By default, uv follows the standard Python dependency resolution strategy of preferring the latest compatible version of each package. But by passing --resolution=lowest, library authors can test their packages against the lowest-compatible version of their dependencies. (This is similar to Go's Minimal version selection.)
> uv allows for resolutions against arbitrary target Python versions. While pip and pip-tools always resolve against the currently-installed Python version (generating, e.g., a Python 3.12-compatible resolution when running under Python 3.12), uv accepts a --python-version parameter, enabling you to generate, e.g., Python 3.7-compatible resolutions even when running under newer versions.
This is great to see though!
I can understand it being a flag on these lower level, directly invoked dependency resolution operations.
While you aren't onto the higher level operations yet, I think it'd be useful to see if there is any cross-ecosystem learning we can do for my MSRV RFC: https://github.com/rust-lang/rfcs/pull/3537
How are you handling pre-releases in you resolution? Unsure how much of that is specified in PEPs. Its something that Cargo is weak in today but we're slowly improving.
- RFC: Rust Has Provenance
-
The bane of my existence: Supporting both async and sync code in Rust
In the early days of Rust there was a debate about whether to support "green threads" and in doing that require runtime support. It was actually implemented and included for a time but it creates problems when trying to do library or embedded code. At the time Go for example chose to go that route, and it was both nice (goroutines are nice to write and well supported) and expensive (effectively requires GC etc). I don't remember the details but there is a Rust RFC from when they removed green threads:
https://github.com/rust-lang/rfcs/blob/0806be4f282144cfcd55b...
-
Why stdout is faster than stderr?
I did some more digging. By RFC 899, I believe Alex Crichton meant PR 899 in this repo:
https://github.com/rust-lang/rfcs/pull/899
Still, no real discussion of why unbuffered stderr.
- Go: What We Got Right, What We Got Wrong
-
Ask HN: What's the fastest programming language with a large standard library?
Rust has had a stable SIMD vector API[1] for a long time. But, it's architecture specific. The portable API[2] isn't stable yet, but you probably can't use the portable API for some of the more exotic uses of SIMD anyway. Indeed, that's true in .NET's case too[3].
Rust does all this SIMD too. It just isn't in the standard library. But the regex crate does it. Indeed, this is where .NET got its SIMD approach for multiple substring search from in the first place[4]. ;-)
You're right that Rust's standard library is conservatively vectorized though[5]. The main thing blocking this isn't the lack of SIMD availability. It's more about how the standard library is internally structured, and the fact that things like substring search are not actually defined in `std` directly, but rather, in `core`. There are plans to fix this[6].
[1]: https://doc.rust-lang.org/std/arch/index.html
[2]: https://doc.rust-lang.org/std/simd/index.html
[3]: https://github.com/dotnet/runtime/blob/72fae0073b35a404f03c3...
[4]: https://github.com/dotnet/runtime/pull/88394#issuecomment-16...
[5]: https://github.com/BurntSushi/memchr#why-is-the-standard-lib...
[6]: https://github.com/rust-lang/rfcs/pull/3469
What are some alternatives?
ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
rust - Empowering everyone to build reliable and efficient software.
nvim-lspconfig - Quickstart configs for Nvim LSP
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
eglot - A client for Language Server Protocol servers
crates.io - The Rust package registry
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
polonius - Defines the Rust borrow checker.
coc-diagnostic - diagnostic-languageserver extension for coc.nvim
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
Bear - Bear is a tool that generates a compilation database for clang tooling.
rust-gc - Simple tracing (mark and sweep) garbage collector for Rust