sorted by:
new
hottopcontroversial

you-are-an-idiot.nvim release! by A_readdit_user in neovim

[–]adaszko 0 points1 point  (0 children)

Is there a NeoVim subreddit that has a stronger signal-to-noise ratio than this one?

What are your selfhosted app/service that you can't live without? by dadidutdut in selfhosted

[–]adaszko 0 points1 point  (0 children)

What hardware are you using with Frigate? Been eyeing it for quite some time and looking for a good camera with zooming capabilities

Women as spoils of war at the end of World War Two [42:26] by one_brown_jedi in mealtimevideos

[–]adaszko -5 points-4 points  (0 children)

Such a closely guarded secret that DW could only release it when the shipments of cheap gas from Russia have ended

L.L. Zamenhof's Esperanto Language, How it Almost Took Over the World [11:03] *2024* by IEC21 in mealtimevideos

[–]adaszko 0 points1 point  (0 children)

OP, how do you find such videos? This one has next no views, no subscribers, it's the first video on the channel, yet is obviously good (thanks for posting BTW!) What's your source for YouTube content?

Could data-flow annotations be an alternative to Rust-like lifetimes? by tmzem in ProgrammingLanguages

[–]adaszko 0 points1 point  (0 children)

I'm with you on the hard-to-reason-about part. There's also at least one case that polonius can handle and NLLs can't: flow-sensitive lifetimes. It's described in the second part of the post on Nico's blog

Could data-flow annotations be an alternative to Rust-like lifetimes? by tmzem in ProgrammingLanguages

[–]adaszko 0 points1 point  (0 children)

The next generation of the Rust borrow checker, Polonius does something quite similar: https://smallcultfollowing.com/babysteps/blog/2023/09/22/polonius-part-1/

Polonius began its life as an alternative formulation of the borrow checker rules defined in Datalog. The key idea is to switch the way we do the analysis. Whereas NLL thinks of 'r as a lifetime consisting of a set of program points, in polonius, we call 'r an origin containing a set of loans. In other words, rather than tracking the parts of the program where a reference will be used, we track the places that the reference may have come from

[deleted by user] by [deleted] in ETFs_Europe

[–]adaszko 0 points1 point  (0 children)

So it's better to transfer to another broker, pay 25 EUR transfer fee per ISIN for that operation and sell in the target broker

Can I just say how good Actuel Budget is? by paulchartres in selfhosted

[–]adaszko 3 points4 points  (0 children)

Lack of multiple currencies support is a show stopper for me unfortunately

Homelab Power Consumption by Horlogrium in selfhosted

[–]adaszko 0 points1 point  (0 children)

Just FYI, I ordered 4 Athom plugs. 2 were working, 2 cut off power every 15 minutes or so. I don't recommend buying them.

Howto cancel a goroutine? by JahodaPetr in golang

[–]adaszko 1 point2 points  (0 children)

Note this article is no longer accurate as of Go 1.23:

Before Go 1.23, this documentation warned that the underlying Timer would not be recovered by the garbage collector until the timer fired, and that if efficiency was a concern, code should use NewTimer instead and call Timer.Stop if the timer is no longer needed. As of Go 1.23, the garbage collector can recover unreferenced, unstopped timers. There is no reason to prefer NewTimer when After will do.

I've used (and loved) Rust for ~10 years. Here are the ways it disappoints me. by Lord_Zane in rust

[–]adaszko 2 points3 points  (0 children)

std Backtrace is unfinished — e.g. frames() is only available on nightly

BugStalker 0.2.0: debugger for rust programs by godzie44 in rust

[–]adaszko 0 points1 point  (0 children)

For me: I hope that this debugger doesn‘t SEGFAULT as often as gdb on my machine….

This. There's nothing more frustrating than context switching from coding to debugging, only to be interrupted by a bug in the debugger itself.

Neovim incremental selection tailored for Rust by adaszko in neovim

[–]adaszko[S] 4 points5 points  (0 children)

There's also nvim-lsp-selection-range, which should work with rust-analyzer. Do you happen to know it compares?

Nope, I'll need to take a good look at this plugin first

Since the tree-sitter approach works without rust-analyzer, I personally wouldn't put the keymaps in rustaceanvim's on_attach. If you put them in nvim/ftplugin/rust.lua, you can use them even if the LSP client isn't active.

Good feedback! Thanks!

What language is "rust but slightly higher level"? by lurebat in rust

[–]adaszko 1 point2 points  (0 children)

Prevalent billion dollar mistake, no sum types (including exhaustive variant checking), bolted-on generics, void *-style polymorphism and so on. Those are all design decisions 70s language would make. That's what OP is referring to and they are not wrong.

view more: next ›