Snow Pettersen

Results 27 issues of Snow Pettersen

The docs on returning a Result from C++ seems to talk a bit about bridging with StatusOr though doesn't provide any examples, so curious what the suggested way of doing...

The editor crashes due to a rust_panic caused by an out of bounds access on a `Vec` whenever move-beginning-of-line (C-a) or move-end-of-line (C-e) is used in a buffer with no...

bug

### Description of the problem / feature request: Allow configuring separate compiler executables when targeting C and C ++respectively, and make this information accessible in Skylark (e.g. add it to...

type: feature request
P4
team-Rules-CPP

From my understanding, there are two ways to customize the output (e.g. using lite_runtime): 1) setting the options on Customize when generating the protos and 2) setting proto options on...

When using the suggested approach of enabling clippy on `build` this also ends up being checked when running the rust-analyzer tool. This ends up being pretty tedious during development since...

question

For a more ergonomic Bazel experience, it would be nice if the test runner would propagate the values of --test_filter to the underlying test runner. Per https://bazel.build/reference/test-encyclopedia seems like this...

question

We have a fairly large Bazel build which generates a .so for use with Android. Incorporating rules_rust into the mix (even as simple as adding a single rust_library with no...

bug

This sets up certstrap for easier import from Bazel projects: with this, certstrap can be imported with the following Bazel WORKSPACE snippet, assuming that Gazelle has been set up in...

I've had some success in integrating certstrap into my Bazel builds to create test certificates. To do so I have to maintain the list of external dependencies within my own...

Brining https://github.com/envoyproxy/envoy/commit/d7edf3bb7411296055171d0394280f9ef03b03fd in results in some issues (see https://github.com/envoyproxy/envoy-mobile/pull/2105) To unblock upgrading we're disabling this change via runtime, but we'll need to figure out the cause of the disruption sometime...