Rust Search
Find the best content on Rust, curated by the community; a
search engine for Rustaceans.
...u32) -> u32 { match n { 1 | 2 => 1, _ => fibonacci(n - 1) + fibonacci(n - 2), } } /// use `Fn`, `FnMut` or `FnOnce` traits to defined JavaScript callbacks /// the return type of callbacks can only be `Result`. #[napi] pub fn get_cwd<T: Fn(String) -> Result<()>>(callback: T) { callback( std::env::current_dir() .unwrap() .to...
...vec_debug => Replaces the default Debug trait implementation with a custom one that prints the bitmask as a vec of all matching values. flags_iter => Adds a ::flags() method that returns an iterator over all flags of the bitmask represented as a tuple (name, flag) . If you need / can think...
...use libproc::libproc::proc_pid; match proc_pid::pidpath(pid) { Ok(path) => println!("PID {}: has path {}", pid, path), Err(err) => writeln!(&mut std::io::stderr(), "Error: {}", err).unwrap() } You can find the latest published release on crates.io You can find the browseable docs for the latest release on docs...
...HList![ isize, bool, &str ] = t3.into(); assert_eq!(h3, hlist![ 999, false, "world" ]); HLists have a hlist_pat! macro for pattern matching; let h: HList!(&str, &str, i32, bool) = hlist!["Joe", "Blow", 30, true]; // We use the HList! type macro to make it easier to write // a type signature for...
...Your code's style should match the existing and surrounding code style. Simple: Your code should accomplish its task as simply and idiomatically as possible. Tested: You must write (and pass) convincing tests for any new functionality. Focused: Your code should do what it's supposed to and nothing more...
...Your code's style should match the existing and surrounding code style. Simple: Your code should accomplish its task as simply and idiomatically as possible. Tested: You must write (and pass) convincing tests for any new functionality. Focused: Your code should do what it's supposed to and nothing more...
...Your code's style should match the existing and surrounding code style. Simple: Your code should accomplish its task as simply and idiomatically as possible. Tested: You must write (and pass) convincing tests for any new functionality. Focused: Your code should do what it's supposed to and nothing more...
...let job = Exec::cmd("sleep").arg("10").start()?; match job.wait_timeout(Duration::from_secs(1))? { Some(status) => println!("finished: {:?}", status), None => { job.terminate()?; job.wait()?; } } License subprocess is distributed under the terms of both the MIT license and the Apache License (Version 2.0). See LICENSE-APACHE and LICENSE...
...For example, it should be possible to only show completions that can lead to a valid Docopt match. This may be hard. (i.e., It may require restructuring Docopt's internals.) Support more shells. (I'll happily accept pull requests on this one. I doubt I'll venture outside of...
...use { solana_program::{entrypoint::ProgramResult, program_error::ProgramError}, spl_tlv_account_resolution::state::ExtraAccountMetaList, spl_transfer_hook_interface::instruction::{ExecuteInstruction, TransferHookInstruction}, spl_type_length_value::state::TlvStateBorrowed, }; pub fn process_instruction( program_id: &Pubkey, accounts: &[AccountInfo], input: &[u8], ) -> ProgramResult { let instruction = TransferHookInstruction::unpack(input)?; let _amount = match instruction { TransferHookInstruction::Execute...
...Lastly, the tap module also has traits TapOptional and TapFallible which run taps on the variants of Option and Result enums, respectively, and do nothing when the variant does not match the method name. TapOptional::tap_some has no effect when called on a None , etc.
...RUSTFLAGS="-Clinker-plugin-lto -Clinker=clang -Clink-arg=-fuse-ld=lld" cargo build Note that the clang version must match the rustc LLVM version . If not, it is possible to encounter errors when running the ethnum-intrinsics build script. You can verify the LLVM version used by rustc with: rustc...
...Myers algorithm has been enhanced with preprocessing and multiple heuristics to ensure fast runtime in pathological cases to avoid quadratic time complexity and closely matches the behavior of gnu-diff and git. The histogram algorithm was originally ported from git but has been heavily optimized. The Histogram algorithm outperforms Myers...
...that case where libEGL.so.1 provides a more recent version of EGL, you can still upcast ths instance to provide version specific features: match egl.upcast::<egl::EGL1_5>() { Some(egl1_5) => { // do something with EGL 1.5 } None => { // do something with EGL 1.4 instead. } }; NixOS A shell...
...Sum, _ctx: &mut Context<Self>) -> Self::Result { msg.0 + msg.1 } } #[actix::main] // <- starts the system and block until future resolves async fn main() { let addr = Calculator.start(); let res = addr.send(Sum(10, 5)).await; // <- send message and get future for result match res { Ok(result) => println!("SUM: {}", result...
...This means that it's important to match whichever regex implementation syntect is using * This is also why fancy's bundled syntax definitions are smaller than onig's default: syntect-onig Feature Desc. syntect-onig / syntect-fancy Enables the minimal feature set that we require from syntect syntect-default-onig...
...use std::path::Path; use std::env; use path_dedot::*; let p = Path::new("../path/to/123/456"); let cwd = env::current_dir().unwrap(); let cwd_parent = cwd.parent(); match cwd_parent { Some(cwd_parent) => { assert_eq!(Path::join(&cwd_parent, Path::new("path/to/123/456")).to_str().unwrap...
...integer, and a float otherwise str::regex_matches 2 String, String Returns true if the first argument matches the regex in the second argument (Requires regex_support feature flag) str::regex_replace 3 String, String, String Returns the first argument with all matches of the regex in the second argument...
...derive(Embed)] #[folder = "$CARGO_MANIFEST_DIR/foo"] struct Asset; include-exclude : Filter files to be embedded with multiple #[include = "*.txt"] and #[exclude = "*.jpg"] attributes. Matching is done on relative file paths, via globset . exclude attributes have higher priority than include attributes. use rust_embed::Embed; #[derive(Embed)] #[folder = "examples/public...
...use num_format::SystemLocale; fn main() { let locale = SystemLocale::default().unwrap(); println!("My system's default locale is..."); println!("{:#?}", &locale); let available = SystemLocale::available_names().unwrap(); println!("My available locale names are..."); println!("{:#?}", available); match SystemLocale::from_name("en_US") { Ok(_) => println!("My system has the 'en_US' locale."), Err...
"You haven’t “fooled” rustc, you are using unsafe code. Unsafe code means that all you can do is fool yourself."