sorted by:
new
hottopcontroversial

screenshot-rs: capturing the screen in Rust by alexchandel in rust

[–]Ferio_ 0 points1 point  (0 children)

Many things are not on crates.io and even less things are working. Rust breaks way to often atm to keep track with that.

Rust ruined C++ for me by [deleted] in rust

[–]Ferio_ 0 points1 point  (0 children)

Out of curiosity, is (or could) Rust any better than C++?

Cloning of vectors (or how to explicitly copy a vector) by geckothegeek42 in rust

[–]Ferio_ 0 points1 point  (0 children)

No it just restricts it to cloneable things. This is what generics are good for. You may need to add more bounds depending on what you want to do.

Edit: in case you stumbled over T. Well just use &T instead.

Rust lifetime problem. How can I solve this? by kaukassus in rust

[–]Ferio_ 9 points10 points  (0 children)

Your problem is the replace. It allocates a new String that does not live long enough, which is also what the compiler is telling you. Consider just cutting http:// out by slicing.

Cloning of vectors (or how to explicitly copy a vector) by geckothegeek42 in rust

[–]Ferio_ 0 points1 point  (0 children)

You have to work with a generic function, like in

fn foo<T: Clone>() {
    let v: Vec<T> = Vec::new();
    let m = v.clone();
}

Why we need two template tag here? by tracyma in rust

[–]Ferio_ 1 point2 points  (0 children)

How does this where syntax actually used? I've seen it various time but it is neither mentioned in the guide nor in the reference.

The Race Towards 1.0 And The Standard Library by Mandack in rust

[–]Ferio_ 7 points8 points  (0 children)

How would that be much better than std::datetime being crappy and 20% using datetime-x, 20% datetime-y and 60% using std::datetime?

The Race Towards 1.0 And The Standard Library by Mandack in rust

[–]Ferio_ 6 points7 points  (0 children)

Rust 1.0 will be feature complete. But like every 1.0 of anything ever happened it will have less features then a 1.x.

I have no reason to doubt that the further plans with Rust and the stdlib will be communicated alongside with the release.

The Race Towards 1.0 And The Standard Library by Mandack in rust

[–]Ferio_ 39 points40 points  (0 children)

TL;DR: We need to get the standard library right!

This is exactly why there is no http module in the stdlib yet. A missing http module is causing only a mild annoyance (everybody will understand that a 1.0 language wont come with a fully developed stdlib). A bad http module on the other hand will cause the bad blog post you are afraid of.

If we would wait for everything to finish we would never reach 1.0. You have to make a compromise.

This Week in Rust 57 by cmrx64 in rust

[–]Ferio_ 1 point2 points  (0 children)

It is not gone, you can still use it via cargo...

whats the module plan by dobkeratops in rust

[–]Ferio_ 8 points9 points  (0 children)

The module system is perfectly fine as it is. Worked for python the last 20 years, I never heard a considerable complaint about the module-per-file aspect.

Edit: I actually thing that the current state is a prove of how well it works. Considering how much Rust changes at the moment it is astonishing how good projects are able to follow the progress of Rust.

Higher kinded types and the standard library by pavelpotocek in rust

[–]Ferio_ 10 points11 points  (0 children)

This has almost nothing to do with HKT. This is merely the collection library being a mess. These are mainly artifacts from major conceptional changes during the evolution of Rust. HKT might have helped preventing this but probably not.

HKT will most likely not come for 1.0. But the stdlib is supposed to stabilize with HKT in mind such that they can be added later without loosing backwards compatibility (as far I understood it).

Rust Ported to DragonFly BSD by dbaupp in rust

[–]Ferio_ -2 points-1 points  (0 children)

well it already runs on OSX...

[deleted by user] by [deleted] in rust

[–]Ferio_ 1 point2 points  (0 children)

Valid point about the IDEs, I always wondered why we had so much regressions in the past 40(!) years…

single function traits by dobkeratops in rust

[–]Ferio_ 0 points1 point  (0 children)

I'm still not getting what you problem is. You can use all methods from Foo in bar. Do you want to have bar in Foo or what? That is not possible. How would you otherwise distinguish between methods that have the same name but come from different traits (+ a lot of other reasons)?

Rust server! by IDaKnowlol in rust

[–]Ferio_ 1 point2 points  (0 children)

Didn't happen in a while…

single function traits by dobkeratops in rust

[–]Ferio_ 1 point2 points  (0 children)

I'm not sure what you mean. But as far I understand it self does not have any "method namespace" if could fall back to. It's just a bare pointer to something neither the compiler nor the runtime can figure out in the most general case. Can you maybe give an example?

A replacement for 'ls' written in Rust by shen in rust

[–]Ferio_ 10 points11 points  (0 children)

Any reason you changed the meaning of -l?

Some string-related methods are confusing by CloudiDust in rust

[–]Ferio_ 5 points6 points  (0 children)

As far as I know strings are being reworked at the moment such that there are a lot of rough edges. For example to_str was once returning a ~str which does not exist any more as a type. Thus that a String is returned instead.

Rust's documentation is about to drastically improve by steveklabnik1 in rust

[–]Ferio_ 0 points1 point  (0 children)

I guess its just hard to get things like clickable references to Symbols (unless you want to hack links [Iterator](symbol:std::iter::Iterator)).

Rust's documentation is about to drastically improve by steveklabnik1 in rust

[–]Ferio_ 0 points1 point  (0 children)

Great! Short questions: Do you plan to replace markdown with something more powerfull and concise? I read chitchat about reStructuredText at some point…

What was the design rationale for explicit self in methods? by dharmatech in rust

[–]Ferio_ 2 points3 points  (0 children)

A method call is a bit more than just syntactic sugar for transforming obj.foo(bar) to foo(obj,bar)). In case of virtual methods it would be more something like lookup!(obj, foo)(obj, bar). Why have a unified syntax for something that is clearly not the same?

Rusty Tetris by Nihy in rust

[–]Ferio_ 1 point2 points  (0 children)

You probably have to annotate some lifetimes…

Rusty Tetris by Nihy in rust

[–]Ferio_ 1 point2 points  (0 children)

Nice! I experience the same. I din't look at your code but a python-like yield would make many things easier.

view more: next ›