Then again, I hear the #rustanalyzer experience isn't as good...

Out of #RAM , #swap full. What could be the reason? Did I go overboard with Firefox tabs? Too many QtCreators? A multitude of open consoles and documents?

Nope. It's stray #rustanalyzer processes eating 15GiB. Or maybe it's #kwrite's fault?

#rust #leak #rls #languageserver

Had some fun on stream exploring #rustanalyzer through a GH issue: https://github.com/rust-lang/rust-analyzer/issues/13002

The developer guidelines/docs were nice and pragmatic, definitely worth a read: https://github.com/rust-lang/rust-analyzer/tree/master/docs/dev

The goal of the issue is to implement completions for extern crate names. I started out getting the completion to work with hardcoded suggestions, which works now. Next time we'll look at sourcing the correct suggestions.

#rust

https://youtu.be/hpMxG5h1Me8

https://github.com/pr2502/ra-multiplex

I feel like it says a lot about #LSP that people feel the need to write a server that wraps a server to avoid spinning up multiple duplicate servers.

#rust #rustanalyzer

Does anyone know how to get my checkmarks to appear? #rust #rustanalyzer #archlinux

#rust 、最初は本当にわからずしんどいんだけど、そのうちなんとなくエラーメッセージとの付き合い方みたいなものが見えてきて「あれ？意外とスムーズに書けるかも」とか思うの面白い。まあ #rustanalyzer はもうすこし頑張ってくれるとありがたいけど。

あと、アレな #cpp コードとか見ると、rustを支持する人たちの気持ちわかるわ…。一種の矯正ギプス的なとこがあるし。

#rust 、最初は本当にわからずしんどいんだけど、そのうちなんとなくエラーメッセージとの付き合い方みたいなものが見えてきて「あれ？意外とスムーズに書けるかも」とか思うの面白い。まあ #rustanalyzer はもうすこし頑張ってくれるとありがたいけど。

あと、アレな #cpp コードとか見ると、rustを支持する人たちの気持ちわかるわ…。一種の矯正ギプス的なとこがあるし。

I have very mixed feelings about #ChatGPT and related large language models (LLMs). They are certainly a cool tool, but I also currently don't believe that these "stochastic parrots" will easily replace search, article/paper writing, coding, and similar tasks. That is, they can be used to augment, but not replace those human activities - at least in the near future.

One more specific example is #Github #Copilot: I am impressed by the code suggested with small "query blocks", either in the form of method signatures or even just comments. While I wouldn't ever just Tab-complete that code into a production codebase (and I hope others also shy away from it), using it as a smarter auto-complete can be a total time-saver. While still learning #Rust, I find it a great tool to provide me with correct syntax while I try to express the semantic concepts in my head. That is, the #VSCode + #Copilot + #rustanalyzer based workflow is a magnitude faster than what I can achieve, at my current level of competence with #Rust, with any other IDE.
However, on the conceptual level, its suggestions range from spot-on (supposedly for parts that have been used in the same form in many Github projects already) to "terrible, awful, don't even think about it". Don't trust the concepts generated by #Copilot, but for getting a concept into correct syntax, it can be a great help.

I find the same to be true of #ChatGPT: it produces correct (human language) syntax, but its concepts on a semantic level are more random than anything else. It doesn't have a reasonable world model, and without such a world model, even internal consistency of statements (let alone factual validity in alignment with what we consider the real world) is darn hard (impossible?) to achieve. It's currently a toy, and should only be used for toy purposes.
On that note, the best use I could personally find for #ChatGPT is to reply to spammers, who operate on a comparable level of factual and consistent concepts (i.e., #BS): https://github.com/rmayr/chatgpt-email

Maybe #ReinforcementLearning will at some point allow LLMs to be factually more accurate, including the ability to cite sources. I don't know, as I'm not an expert in this field. But the current #UnsupervisedLearning approaches with just scraping massive amounts of (syntax, but not semantic) web content seem fundamentally flawed to me.

On a sidenote, if the #OpenAI mission is really to "ensure that artificial general intelligence benefits all of humanity", shouldn't the trained models be, erm, #open (source)? After all, the training data is publicly generated, so it seems more beneficial to humanity if the derivations are also #open for building upon them.

Been re-writing my neovim config tonight with lua. Trying to understand the things and not just blindly copy paste stuff. Happy that a bunch of tpope’s plug-ins do still work #neovim #lua #RustLang #RustAnalyzer

Anyone had any luck getting `rust-analyzer` extension's intellisense to work in VSCode using a #Nix `flake` development environment?

#VSCode #RustLang #Rust #Intellisense #RustAnalyzer #NixOS #Development #SoftwareEngineering #WSL2 #WSL

Anyone had any luck getting `rust-analyzer` extension's intellisense to work in VSCode using a #Nix `flake` development environment?

#VSCode #RustLang #Rust #Intellisense #RustAnalyzer #NixOS #Development #SoftwareEngineering

okay is there #RustAnalyzer for #lapce? #rust #rustlang

Oh no! 😱 rust-analyzer is eating all my RAM - *nom nom nom nom* 😋

Well, having two Rust projects open at the same time is just too delicious i guess...¯\_(ツ)_/¯

#Rust #RustLang #RustAnalyzer #Memory #Programming #RAM #NomNom

One of my favourite #rust debugging features is the dbg!() macro - I wrap it around values of interest and look through the trace.

My one annoyance with it is that to remove them again it's a bit less convenient, since you have to remove the "dbg!(" and the ")" separately instead of just a whole print line.

During this morning's #AdventOfCode2022 I thought "Oh, maybe I can add an action to #rustanalyzer to do that."

I don't have to, it's already there!

Lately I've been a bit worried about the massive amount of disk writes by some software. Normally, I wouldn't mind at all, it's an SSD anyway, so write all you want. But it IS also an SSD. It has a total amount of writes, and after that, it's gonna be dead, and guess who will have to pay for a new one...

#Rust #RustAnalyzer #Firefox #Systemd #Cargo

I had some fun with #rust over the last weeks. From time to time I worked on https://github.com/aixigo/PREvant/pull/104

The fun included:

- updating crates and handling breaking changes. #rustanalyzer and #neovim helped me at lot.
- improve configuration handling with figment. Really nice crate.
- passing #docker login information around to pull from any private #dockerregistry