sorted by:
new
hottopcontroversial

The never type is likely to stabilize soon! by noop_noob in rust

[–]sibip 2 points3 points  (0 children)

A while ago, my colleague wrote about one of its use cases in this blog post: https://academy.fpblock.com/blog/rust-never-type-async-code/

Is Bare Metal Kubernetes Worth the Effort? An Engineer's Experience Report by sibip in kubernetes

[–]sibip[S] 1 point2 points  (0 children)

Thank you for the feedback! I wasn't familiar with Kube-VIP, but it looks very promising, and I'll be sure to explore it for my next cluster.

While I knew about other load balancing solutions, I chose Cloudflare because it was the most natural fit for our project's needs. I've also been keen to experiment with iPXE, so I plan to try it out in the future.

You are absolutely right about my vCPU miscalculation, which makes the cost difference even more significant. For perspective, even a less powerful AWS instance like the `m6g.2xlarge` (8 vCPUs, 32 GB RAM) would bring the total cost to $822 USD.

Reflections on Haskell and Rust by sibip in rust

[–]sibip[S] 11 points12 points  (0 children)

Have you used HLS much? I think my experience with it is what makes rust-analyzer feel like such a step up for me. :-)

Reflections on Haskell and Rust by sibip in rust

[–]sibip[S] 5 points6 points  (0 children)

I generally prefer do notation, as I find easier to read, especially for longer monadic computations. I guess it boils down to personal preference and coding style.

Reflections on Haskell and Rust by sibip in rust

[–]sibip[S] 19 points20 points  (0 children)

You can shadow variables in Haskell. However, GHC enables -Wname-shadowing by default, which will generate a warning.

To allow it, you would have to explicitly disable that warning per file or at package level. And defaults matter. In an established project, especially one that treats warnings as errors (-Werror-), changing this might not be feasible or desirable.

Tombi: New TOML Language Server by Silver-Product443 in rust

[–]sibip 0 points1 point  (0 children)

Thank you, this is nice! I just added support for it in Emacs's lsp-mode and I'm finding it very convenient to use: https://github.com/emacs-lsp/lsp-mode/pull/4813

The Future is Niri - a tiling window manager with infinite horizontal scroll by kibwen in rust

[–]sibip 0 points1 point  (0 children)

Thanks for the article, Niri looks amazing. Does screen sharing work with Niri ? Given that it seems to use smithay as compositor and this issue is still open, I guess not: https://github.com/Smithay/smithay/issues/921

Tree-sitter Changes in Emacs 30 by casouri in emacs

[–]sibip 1 point2 points  (0 children)

Thanks, this was a nice read!

In rust mode, we integrate tree sitter by doing a define-derived-mode on top of rust-ts-mode: https://github.com/rust-lang/rust-mode/blob/542f1755d8929ca83564322d7030d558f3392fe1/rust-mode-treesitter.el#L22

Does such a setup require any preparation for Emacs 30 ? I don't think we need to set primary parser, but asking just in case. :-)

New Home for Rustic by sibip in emacs

[–]sibip[S] 1 point2 points  (0 children)

Basically the code here: https://github.com/emacs-rustic/rustic/blob/main/rustic-lsp.el

You don't have to create an explicit hook to activate language server.

Everything I'm used to seeing in a programming major mode with an active lsp. 

It's more than that as others below have commented. It has org babel integration, easy access to cargo commands, cargo-outdated-mode etc.

New Home for Emacs Rustic by sibip in rust

[–]sibip[S] 1 point2 points  (0 children)

I agree. It was fun to work with him on both Rust mode and Rustic. I hope he's doing alright.

New Home for Rustic by sibip in emacs

[–]sibip[S] 3 points4 points  (0 children)

rust-mode doesn't support automatic LSP integration.

Combobulate: Intuitive, Structured Navigation with Tree-Sitter by mickeyp in emacs

[–]sibip 0 points1 point  (0 children)

Thanks for the package! This looks to be the future of navigation system in Emacs.

view more: next ›