What is the feature ?

I'm trying out this library for the first time and I'm seeing several places where some shorthand functions would have been really pleasant:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. My plots are supposed to be white-on-black, which requires a lot of boilerplate on lots o

It might be worth considering adding simd-json to the TechEmpower benchmarks:

https://github.com/TechEmpower/FrameworkBenchmarks/blob/cfbbf5d11143c96851620eb1aeaf3c2893e862c9/frameworks/Rust/actix/src/main.rs#L23

To make this really worthwhile #121 would be good.

suggested by @pickfire

On my system:

$ cat /sys/class/power_supply/BAT0/model_name
5�+1^^�^^�9(-:'&��

Or:

$ hexdump /sys/class/power_supply/BAT0/model_name
0000000 8035 312b 801e 801e 2839 3a2d 2627 8080
0000010 000a
0000011

This means trying to get battery info always returns an error due to https://github.com/svartalf/rust-battery/blob/master/battery/src/platform/linux/device.rs#L36

Hi! I am very new to Rust, so I apologize if this ends up being a naive question.

So, for my robot motion optimization application, I have created an objective function and gradient function in the required format using closures, but the closure types are FnMut’s rather than Fn’s. This leads to the compiler complaining since the OpEn library forces the objective and gradient functions to be F

Reader functions can take in a Read + Seek trait impl, write can write to a Write

sharksforarms/deku#100

Feature gated under "std" feature as these are std traits.

For nostd, maybe need to wait for: rust-lang/rust#48331

References:
https://doc.rust-lang.org/std/io/trait.Read.html
https://doc.rust-lang.org/std/io/trait.Write.ht

https://github.com/dtolnay/trybuild

This would let us declare things that should fail and then check that they really do fail.

Specifically, we could make a test such as

#[derive(Zeroable, Pod)]
pub struct Bad(u16, u8);

And that should fail to derive, of course.

flatc has rich set of arguments https://google.github.io/flatbuffers/flatbuffers_guide_using_schema_compiler.html

I saw you implement the basic set that works just fine, but for example I'd love to modify the --filename-suffix, but cannot findout how?

Help would be much appreciated!

Expand the available list of system metrics. Around 10-15 new metrics (the most useful we can think of) is a good start.