Teoh Han Hui
Teoh Han Hui
``` Compiling portable-atomic v0.3.19 {standard input}: Assembler messages: {standard input}:80: Error: selected processor does not support `casp x6,x7,x4,x5,[x0]' {standard input}:103: Error: selected processor does not support `caspa x6,x7,x4,x5,[x0]' {standard input}:126:...
### Feature Description: Publish a pre-built AppImage for the aarch64 (ARM64) platform.
Compare https://github.com/automerge/automerge/blob/bf4607c2acb55be5948911c0167cbfd65aa80a96/rust/automerge/src/value.rs#L604-L671 to the Rust API guidelines: https://rust-lang.github.io/api-guidelines/naming.html#ad-hoc-conversions-follow-as_-to_-into_-conventions-c-conv Many of the methods seem to be named incorrectly, e.g. `to_str` should actually be `as_str`.
It makes sense internally for the library, but an "external ID" is redundant naming for consumers of this library.
Usage example (`input.conf`): ``` Ctrl+r script-message-to fuzzydir rescan-paths ; script-message-to sub_select select-subtitles ``` The `observe_property` is necessary because setting properties seems to happen asynchronously, which means `rescan-external-files` would not be...
Perhaps related to #302, I'd like to be able to prevent parsing of options after positionals. Given: ``` Usage: krun [--net=NET_MODE] [--passt-socket=PATH] COMMAND [COMMAND_ARGS]... Available positional items: COMMAND the command...
Given this test: https://github.com/staltz/callbag-share/blob/d96748edec631800ec5e606018f519ccaeb8f766/test.js#L93-L203 If `sinkA` sends a pull asynchronously but immediately(*), then it can happen that `sinkB` has sent its handshake to `share`, but has not yet received back...
I'm trying to understand how to produce a stream which combines inputs from multiple streams.
I can't figure out how to use `CobsDecoder`. It doesn't seem to me like the current design of `CobsDecoder` allows it to be reused for decoding the next message? https://github.com/jamesmunns/cobs.rs/blob/674fd038133e185ad7d90982610f494f6d8a20ee/src/dec.rs#L256...
> > This crate has two features: > - ... > - `crossterm-support`: Provides a wrapper type that let's [`crossterm`][crossterm] use xterm.js as a backend (located [here][crossterm-support]). This enables xterm.js...