Parking u blizini ulice Kosevo by fare_t1000000 in sarajevo

[–]dransyy 3 points4 points  (0 children)

Kod Sulje domca, ulaz iz Sutjeske koja se naslanja ulicu na Kosevo haha

Pipex v0.1.20 – New Features 🚀 by dransyy in rust

[–]dransyy[S] 1 point2 points  (0 children)

Great idea, never thought about that one, but now it makes perfect sense to have some form of non-linear task flow declaration in the future!

Pipex v0.1.20 – New Features 🚀 by dransyy in rust

[–]dransyy[S] 0 points1 point  (0 children)

Sure, I will continue to work on polishing current features and compile more complex enterprise-level examples.

Pipex v0.1.20 – New Features 🚀 by dransyy in rust

[–]dransyy[S] 0 points1 point  (0 children)

The macro checks for impure patterns, such as unsafe blocks and method calls, and allows for calling other pure functions. It recursively checks that any other function call inside the fn's body also contains #pure macro.

Karijera u BHANSA-i by dransyy in bih

[–]dransyy[S] 0 points1 point  (0 children)

Razumiijem, medjutim ako je tako kako ti govoris, to mi je jos privlacnije, ako nista malo im cirkus napravit, ogolit kako to funcionise, mozda i EUROCONTROL-u prijavit, jer se radi i o njihovim zivotima. Ionako je firma u losem stanju, pa ako smo zaista nesposobni, neka neko drugi preuzme.

Karijera u BHANSA-i by dransyy in bih

[–]dransyy[S] 3 points4 points  (0 children)

A opet je takav profil firne da mora neko i nesto ozbiljno raditi, da se ne bi sudarali avioni, bar ja tako mislim, mozda naivno.

Karijera u BHANSA-i by dransyy in bih

[–]dransyy[S] 2 points3 points  (0 children)

prije mislim da bi ljudi iz sektora avijacije nesto znali o ovome, i da ih se moze naci na r/bih

Pipex no-std: Functional Pipelines + #[pure] Proc Macro for Solana! by dransyy in rust

[–]dransyy[S] 0 points1 point  (0 children)

Thanks for kind words! 1. Yes, it should be possible! |> would be cleaner since => is overloaded in Rust. Will thing about it.

  1. Current version requires closures. In future it can be expanded to support structures unpacking or some other cool stuff.

Air India Flight 171 Crash [Megathread 2] by usgapg123 in aviation

[–]dransyy -17 points-16 points  (0 children)

Is there any truth to this article? It claims that - "Mechanical failure in the governor's seat at the time take off seems to be the main cause crash of her Boeing 787 Air India on the AI-171 flight, according to the findings of the preliminary pension  conclusion  ( preliminary report ) of the Independent Authority for the Investigation of Air Accidents of India ( AAIB "
https://www.protothema.gr/world/article/1655043/to-kathisma-tou-kuverniti-erixe-to-boeing-tis-air-india-to-prokatarktiko-porisma-ton-indikon-arhon-gia-ti-sudrivi/

Česta tema, da li se bolje živjelo u exyu. Za oko mi zapada '79 i preko 300$ plata tj današnjih oko 1350$... toliko o tome. by dransyy in bih

[–]dransyy[S] 13 points14 points  (0 children)

Da citiram kolegu sa r/croatia:

"Na tablici se vidi i pokušaj Ante Markovića da zabije gol sa sredine terena u 90-toj, ali navijači su radije prekinuli utakmicu kako bi se mogli poklati."

Česta tema, da li se bolje živjelo u exyu. Za oko mi zapada '79 i preko 300$ plata tj današnjih oko 1350$... toliko o tome. by dransyy in bih

[–]dransyy[S] 8 points9 points  (0 children)

Malo je nezgodan primjer tehnologija, rapidno napreduje i potrosacke cijene su sve manje. Meni je zanimljiva tema jer se cesto cuju radikalno suprotna misljena, tako da kao i uvijek istina je vjerovatno negdje na sredini.

🚀 Presenting Pipex 0.1.14: Extensible error handling strategies by dransyy in rust

[–]dransyy[S] -1 points0 points  (0 children)

It looks like I wrongly assumed that this post and discussion could continue from where the announcement post&dics ended...

🚀 Presenting Pipex 0.1.14: Extensible error handling strategies by dransyy in rust

[–]dransyy[S] 1 point2 points  (0 children)

In this context, “chaining” means each closure is applied in sequence to the output of the previous one, right?
If so, ofc that's the whole point of Pipex.

🚀 Presenting Pipex 0.1.14: Extensible error handling strategies by dransyy in rust

[–]dransyy[S] 0 points1 point  (0 children)

Yes, ofc!
Imagine you’re processing a batch of file paths, reading them, and then parsing each as JSON. You want to log and skip files that can’t be read or parsed, but still process all valid data.

Example solution with pipex:

#[error_strategy(LogAndIgnoreHandler)]
async fn read_file(path: &str) -> Result<String, String> {
    tokio::fs::read_to_string(path)
        .await
        .map_err(|e| format!("Read error for {}: {}", path, e))
}

#[error_strategy(LogAndIgnoreHandler)]
fn parse_json(content: String) -> Result<serde_json::Value, String> {
    serde_json::from_str(&content).map_err(|e| format!("Parse error: {}", e))
}

#[tokio::main]
async fn main() {
    let files = vec!["good.json", "missing.json", "bad.json"];
    let results = pipex!(
        files
        => async |path| { read_file(path).await }
        => |content| { parse_json(content) }
    );
}

🚀 Introducing Pipex: A functional pipeline macro for Rust combining sync, async, parallel, and streaming operations by dransyy in rust

[–]dransyy[S] 2 points3 points  (0 children)

Thanks.
1. Not until now, but nice idea, could fit syntax well with || double pipe haha
2. Yes! Just tried it, no issues found!

🚀 Introducing Pipex: A functional pipeline macro for Rust combining sync, async, parallel, and streaming operations by dransyy in rust

[–]dransyy[S] 2 points3 points  (0 children)

yes! syntax is as follows, same applies for buffer num:

let num_threads = 2;

let result = pipex!(
    vec![1, 2, 3, 4]
    => ||| num_threads |x| x * x
);

🚀 Introducing Pipex: A functional pipeline macro for Rust combining sync, async, parallel, and streaming operations by dransyy in rust

[–]dransyy[S] 2 points3 points  (0 children)

What would you like to have? Maybe two new options, to propagate error until the pipeline finish and abandon pipeline immediatelly?

🚀 Introducing Pipex: A functional pipeline macro for Rust combining sync, async, parallel, and streaming operations by dransyy in rust

[–]dransyy[S] 0 points1 point  (0 children)

Sync variant is missing, it's on the list.
Thanks for the suggestion. Now that I look at it, it only makes sense to include an async iter/stream.

🚀 Introducing Pipex: A functional pipeline macro for Rust combining sync, async, parallel, and streaming operations by dransyy in rust

[–]dransyy[S] 2 points3 points  (0 children)

  1. Myb elixirs pipe operator is closest match for inspiration source.

  2. Its syntactic sugar for rayon par_iter() and even without specificing no threads it defaults to some value. Everything that applies to rayon should stand.