🦀 #RustChallenge 🦀
#rust #rustlang #programing #dev #EZ
1. Both runs and gives the output
2. CODE No2 gives output and A gives overflow error
3. CODE No2 gives output and B gives error
4. Both gives error
vote in channele and DONT FORGET TO JOIN OUR FAMELY
#rust #rustlang #programing #dev #EZ
// CODE No1What will be the outcome?
fn main(){
let x = 2;
assert_eq!(x,2_i8);
println!("{}",x.pow(6));
}
// CODE No2
fn main(){
let x = 2;
println!("{}",x.pow(6));
}
1. Both runs and gives the output
2. CODE No2 gives output and A gives overflow error
3. CODE No2 gives output and B gives error
4. Both gives error
vote in channele and DONT FORGET TO JOIN OUR FAMELY
Learning Rust Part 1: A kitten's guide to Options and Results
https://cherrykitten.dev/blog/rust-1-options-results/
https://cherrykitten.dev/blog/rust-1-options-results/
#RustChallenge 🦀🦀
What is the result?
A. Prints 1 (explain how)
B. Prints 2 (explain how)
C. Error (explain why)
✨vote in channele and don't forget to join our rust family❤️
What is the result?
A. Prints 1 (explain how)
B. Prints 2 (explain how)
C. Error (explain why)
✨vote in channele and don't forget to join our rust family❤️
The New Website and Release for the KCL Programming Language Written by Rust:
https://kcl-lang.io/blog/2022-kcl-0.4.5-release-blog/
https://kcl-lang.io/blog/2022-kcl-0.4.5-release-blog/
kcl-lang.io
KCL v0.4.5 Release Blog | KCL programming language.
Introduction
🦀 #RustChallenge #ez😋
ANSWER IN CHANNEL AND JOIN FOR MORE FUN😜😜
WHAT WILL PRINT??
A. RUST
B. js
C. RUSTjspython
D. ERROR 404
ANSWER IN CHANNEL AND JOIN FOR MORE FUN😜😜
WHAT WILL PRINT??
A. RUST
B. js
C. RUSTjspython
D. ERROR 404
https://diff.rs/
View the differences between Rust crate versions. Enter a crate name such as serde in the search field in the top-right corner to get started.
This is an experimental WASM-based web application written in Rust with Yew that uses the crates.io API to fetch crate metadata, fetch and parse the crate source, unpack it in-memory and render a diff in the browser.
Source code for this application is available at github.com/xfbs/diff.rs.
View the differences between Rust crate versions. Enter a crate name such as serde in the search field in the top-right corner to get started.
This is an experimental WASM-based web application written in Rust with Yew that uses the crates.io API to fetch crate metadata, fetch and parse the crate source, unpack it in-memory and render a diff in the browser.
Source code for this application is available at github.com/xfbs/diff.rs.
GitHub
GitHub - xfbs/diff.rs: Web application to render a diff between Rust crate versions. Implemented in Yew, runs fully in the browser…
Web application to render a diff between Rust crate versions. Implemented in Yew, runs fully in the browser as WebAssembly. - xfbs/diff.rs
https://tavianator.com/2023/irregex.html
Regular expressions are fascinating to me. On one hand, they can be extremely succinct, expressive, and efficient. On the other hand, they can be basically write-only. They come with a simple but powerful theory that leads to efficient implementations. Sadly, many implementations ignore the theory in order to offer additional features, at the cost of worst-case exponential complexity.
It is possible, however, to implement some of those additional features, and still operate in worst-case linear time. The implementation (~400 lines of Rust) even fits in a single blog post! The full code is on GitHub, and the commit history lines up with the blog post if you want to follow along.
Regular expressions are fascinating to me. On one hand, they can be extremely succinct, expressive, and efficient. On the other hand, they can be basically write-only. They come with a simple but powerful theory that leads to efficient implementations. Sadly, many implementations ignore the theory in order to offer additional features, at the cost of worst-case exponential complexity.
It is possible, however, to implement some of those additional features, and still operate in worst-case linear time. The implementation (~400 lines of Rust) even fits in a single blog post! The full code is on GitHub, and the commit history lines up with the blog post if you want to follow along.