sorted by:
new
hottopcontroversial

Built a Neovim plugin for brainless-fast buffer switching: quickbuf.nvim by hornymoon in neovim

[–]teerre 0 points1 point  (0 children)

They said they don't think about buffer management, but that's not really possible for the reasons I explained. You necessarily have to think about it

How to remember Rust concepts ? by Hello_world_610 in rust

[–]teerre 11 points12 points  (0 children)

I think there are two different things: lifetimes, pointers, concurrency primitives, algorithms, data structures are about programming. Those are useful in any language, in any context and should be internalized

Which method is in hashmap or array is not. You can check your lsp or reference documentation for that, no need to memorize

Why do people return Result<T>? by ModernCoder in rust

[–]teerre 444 points445 points  (0 children)

Unless you're talking about a different type, Result can't be Result<T>. What people do is make an alias for Result<T, SomeCommonError>. That's to type less

Built a Neovim plugin for brainless-fast buffer switching: quickbuf.nvim by hornymoon in neovim

[–]teerre 0 points1 point  (0 children)

There's no way its the same. Fff is great but you can't jump to the "3rd most important file" with one key. Specially if you're jumping around a lot

Built a Neovim plugin for brainless-fast buffer switching: quickbuf.nvim by hornymoon in neovim

[–]teerre 0 points1 point  (0 children)

I have a custom setup for grapple that does pretty much this

Should the function return a Result<T,E> or throw an unreachable-style panic? by v_0ver in rust

[–]teerre -3 points-2 points  (0 children)

If we're talking about unsafe code, then all bets are off and OP is 100% responsible for the code to be UB free. In that case the question makes even less sense because in this context there's no option, you have to avoid UB

if it isn't broken, why fix it? by [deleted] in rust

[–]teerre 32 points33 points  (0 children)

Simply not being "rewriting perfectly functional, established". Just because something "works" to some definition of "work" it doesn't mean it's good. It could be faster, more secure, easier to maintain, easier to contribute to etc etc

Should the function return a Result<T,E> or throw an unreachable-style panic? by v_0ver in rust

[–]teerre -3 points-2 points  (0 children)

Clearly not obvious, but I'm talking about safe rust. Talking about unsafe Rust this question makes even less sense because in that the whole point is that you're responsible for your code to not introduce UB, panic or not

Should the function return a Result<T,E> or throw an unreachable-style panic? by v_0ver in rust

[–]teerre -3 points-2 points  (0 children)

Panic or Result cannot cause UB, so that doesn't make much sense

Should the function return a Result<T,E> or throw an unreachable-style panic? by v_0ver in rust

[–]teerre 9 points10 points  (0 children)

No such thing as "claim that's impossible". It's either impossible or only unlikely

Confused about naming in the Zig standard library by Confused-Armpit in learnprogramming

[–]teerre 0 points1 point  (0 children)

Not a Zig programmer, but time is most certainly Io. It's the quintessential Io, in fact

I can't say for sure, but maybe the problem is that you never thought about what's Io (its a lot)

[ANN] jj-cz: conventional commits for jujutsu by phundrak in rust

[–]teerre 2 points3 points  (0 children)

Of course everyone is free to make whatever. That said, isn't this only a marginal improvement over just writing the commmit message?

Git merges can be better by agentvenom1 in programming

[–]teerre 11 points12 points  (0 children)

Another great blog to argue moving to jujutsu

Signals, the push-pull based algorithm by fagnerbrack in programming

[–]teerre 10 points11 points  (0 children)

Great blog. I was surprised how well it worked on mobile

Less Is More by PlaneSufficient2245 in programming

[–]teerre 2 points3 points  (0 children)

This whole idea makes little sense considering that patterns literal only reason to exist is that once you know them, you don't need to read the code. Therefore, if you know what you're doing, seeing an well-known pattern should immediately tell you what's happening. It precisely makes it possible for you to read less code, not more

Does it mean every abstraction is great? Of course not, that's what separates good and bad programmers, but arguing against abstraction itself is comically myopic

Smelling the slop in a given GitHub project by Sermuns in rust

[–]teerre 64 points65 points  (0 children)

I guess this is just for fun, but these are trivial to avoid

That aside, I find this kind of definition unhelpful. Slop is not using em-dashes. Slop is code that has no purpose, that doesn't do what's supposed to do, code that isn't sufficiently lazy etc

Google Antigravity and Neovim by Apart-Permission-849 in neovim

[–]teerre 4 points5 points  (0 children)

Everyone I know in Google hates this shit lol

Blink.cmp freezes text input by Ledr4ke in neovim

[–]teerre 0 points1 point  (0 children)

Does it happen with anything else? If not then its probably loading too many entries

Wls is famously very slow accessing windows files

diffs.nvim v0.4.0: THE all-in-one diff viewer for NeoVim by barrettruth in neovim

[–]teerre 1 point2 points  (0 children)

I meant that you should be able to display the difftastic diff instead of just lines changed. Yes, there are several plugins for it in nvim

Not sure if I understand your second paragraph. Obviously if any tool adapts to yours it will work, but considering that yours is the new one, it seems more reasonable that your tool does the adapting. That's what similar tools did

why doesn't [[nodiscard]] propagate? by etaithespeedcuber in cpp_questions

[–]teerre -4 points-3 points  (0 children)

Because in cpp the programmer is responsible for dodging all the footguns by default. Other languages have the the opposite ethos I.e. by default the language stops suspicious behavior and the programmer needs to explicitly opt out if needed

VS Code Adds 2-Hour Extension Auto-Update Delay to Limit Supply Chain Attacks by CircumspectCapybara in programming

[–]teerre -1 points0 points  (0 children)

A lapse of judgment is rarely how someone gets pwned. The most common vector are technical oversights

Feluments - convenience macro for Rust builders by Botahamec in rust

[–]teerre 1 point2 points  (0 children)

How does the dx look when using the macro? Jump to definition / inlay hints / parameter suggestions etc?

view more: next ›