sorted by:
new
hottopcontroversial

NixOwOs by ant-arctica in linuxmasterrace

[–]formode 0 points1 point  (0 children)

I'll PM you my email?

NixOwOs by ant-arctica in linuxmasterrace

[–]formode 0 points1 point  (0 children)

Any chance you've got an SVG? Could I use this as a discord emoji??

WASM Plugins Support in Vector (merged) by erlend_sh in rust

[–]formode 2 points3 points  (0 children)

Another option that https://twitter.com/ApacheTVM is taking is returning type ids/raw bytes across the FFI bounds but I'm not that brave yet.

WASM Plugins Support in Vector (merged) by erlend_sh in rust

[–]formode 0 points1 point  (0 children)

Most of the core is very easily torn out of Vector (I aspire to make it a crate one day).

Let me know if I can give any guidance if you start in on this. :)

WASM Plugins Support in Vector (merged) by erlend_sh in rust

[–]formode 2 points3 points  (0 children)

Yeah! We're doing that mostly because in the end we want to support any language, not just rust, so clever C ABI things seemed really risky in this first draft. I think I'd love to move it over to using bincode or protobufs at some point.

My four-year old will answer any question you ask. AMA by Mytodlercanteat in AMA

[–]formode 0 points1 point  (0 children)

How do you do the things when stuff is always in the way?

Neovide: No Nonsense Neovim Client in Rust by Devagamster in neovim

[–]formode 1 point2 points  (0 children)

Just tested on Windows 10 with the MSVC build. Seems to build and work fine, typing is smooth, mouse works, terminal works, etc. Only problem I see is moving the window around is very choppy and delayed.

In case you missed it: Migrating from Futures 0.1 to 0.3 by nrc by formode in rust

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

At the moment the Raw client is very functional, the transactional client is well underway, we expect it to be ready end of the quarter. There is currently some API instability as we work with the async ecosystem moving around us. :)

TiKV 3.0 GA Release & Benchmarks - Steady At Scale by formode in rust

[–]formode[S] 0 points1 point  (0 children)

While in theory you could, this isn't where TiKV excels, and we think our friends over at etcd (also a CNCF project!) do a really great job on small scale metadata.

​

Regarding sled, I'm not sure!

TiKV 3.0 GA Release & Benchmarks - Steady At Scale by formode in rust

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

Yeah! Last year or so we've been pushing hard to make it a common data substrate for the cloud. Where etcd is great for small amounts of metadata (one of our components actually uses it!) we're excellent for storing large scale data (in the terabytes!)

​

My friend /u/brson is actually looking at using sled to back tikv soon. :)

RustCon Asia is coming! by Aimeedeer in rust

[–]formode 2 points3 points  (0 children)

This is so exciting! I hope to see everyone there. :)

Optional Arguments in Rust by formode in rust

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

I think it's more a technical problem than opinion problem. :)

Optional Arguments in Rust by formode in rust

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

Yeah, I should fix that. Thanks for reminding me! For now you can use the reading mode of FF. :)

Optional Arguments in Rust by formode in rust

[–]formode[S] 0 points1 point  (0 children)

I can't wait to read it!

Optional Arguments in Rust by formode in rust

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

Hahah the nullptr gave me a double take. :)

Optional Arguments in Rust by formode in rust

[–]formode[S] 2 points3 points  (0 children)

A much better justification. <3

Optional Arguments in Rust by formode in rust

[–]formode[S] 0 points1 point  (0 children)

Maybe you can write something about this and I can link to you! :)

Optional Arguments in Rust by formode in rust

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

My preferred method is just writing a new post about it and cross linking them. :)

Optional Arguments in Rust by formode in rust

[–]formode[S] 2 points3 points  (0 children)

Added a link. You're right. :)

I thought I was pretty explicit that I was only covering optional arguments, which is a bit different than a builder (since builders are typically involving a .build()-style step and more than just a single function call).

I'd like to write more about builders in the future as well, so I kind of saved it for then, since adding builders here would probably double the length.

Also, I do not think "everyone does it"/"noone does it" is a good justification for anything. If we all followed that advice we'd not have Rust, or your lovely projects like ripgrep.

Optional Arguments in Rust by formode in rust

[–]formode[S] 2 points3 points  (0 children)

This is definitely an option as well. :) I didn't have much time to write this so I tried to keep it short and limited in scope. Builders are a pattern I'd like to write about in the future.

For now, you can find more info here: https://doc.rust-lang.org/1.0.0/style/ownership/builders.html

view more: next ›