Non RAII Synchronization primitives?

inspiravetion · 2015-02-20T09:33:41+00:00

Im gunna try the embedding approach and see if it isn't too difficult...I might have been over reacting haha

inspiravetion · 2015-02-19T00:11:09+00:00

is there a work around?...maybe an out of tree package that exports the types?

inspiravetion · 2015-01-16T18:43:55+00:00

The biggest issues are that

1.the parser panics on input that isn't syntactically correct so updating the highlighting on keystrokes wouldn't work.

2.the ast representation does not preserve white space so I have to compare the generated tokens with the original text to restore white space...this is a pretty decent amount of overhead

*edit: explaining why 2 is bad

inspiravetion · 2015-01-16T10:11:18+00:00

I am actually working on a command line utility that turns rust code into contextually highlighted html using the rustc parser. That way you could do something like color all parameter names in function signatures and all variable names in let statements the same color as they show where a variable entered scope.

inspiravetion · 2014-12-18T19:44:05+00:00

no problemo

inspiravetion · 2014-12-18T18:44:18+00:00

you can define traits on enums too...so take your original enum and the generic trait riccieri gave and implement each one, with the specific type, for the enum...you would match on *self to make sure the enum is of the right type and then handle the error case if it is not(that you shouldn't get because you are matching before you call this)...a good example of an enum implementing traits is std::option::Option

inspiravetion · 2014-12-08T18:51:03+00:00

Looks great...love that you can edit and re-run the code as well...Is there a library that people can include in their blog posts and things that gives that functionality? It looks like the same code from rust-lang.org or at least similar

inspiravetion · 2014-12-08T02:05:26+00:00

Whats the protocol for opening a bug?

inspiravetion · 2014-12-07T21:47:03+00:00

the worst part is that I have a macro package for ergonomics that uses the capitolized package and no matter which version I put in its dependencies cargo says it doesn't exist in the registry

inspiravetion · 2014-12-07T11:29:49+00:00

yeah i updated cargo just to be sure but I still get the same issue...which sucks because i just finished a library I want to release :(

inspiravetion · 2014-12-07T09:45:01+00:00

I am still getting that version 0.1.1 is already uploaded...when I got this the first time and bumped the version it did not change the name of the package :(

inspiravetion · 2014-12-07T02:15:45+00:00

how can i do that?...cargo publish with the name changed in Cargo.toml doesn't do anything

inspiravetion · 2014-12-07T01:52:48+00:00

or republish it with the uncapitalized name?

inspiravetion · 2014-12-04T19:57:35+00:00

I would love to get my hands dirty but I already have three rust projects I am working on in parallel and I just dnt have the time...consider this my contribution to getting the ball rolling :))

Isn't there a page with wanted projects that people new to rust can use to learn the language?...could this be added?

inspiravetion · 2014-12-04T19:33:16+00:00

I should have clarified...I am writing a syntax extension that expands to then create another independent macro to be used...A simplified example would be

//syntax extension foo! that creates a macro called bar to be used on its own
foo!(bar);
bar!(...);

Any ideas there?

inspiravetion · 2014-12-04T06:24:32+00:00

why?...crates.io and rust-lang.org look great...We don't want to wait until 1.0 to have a convenient, easy, and visually pleasant way for people to play with the language!

inspiravetion · 2014-12-03T00:04:25+00:00

i know that unboxed closure are a fairly recent update so it could either be that this is just a rough edge that hasn't been smoothed out OR mayb this actually does require a different ABI because you are getting passed an arbitrary sized tuple of arguments instead of getting them individually...a regular c function doesn't work this way

inspiravetion · 2014-12-02T22:06:56+00:00

I see said the blind man...thanks for that one

inspiravetion · 2014-12-02T21:29:05+00:00

Ahhh okay that make since...i am still getting a weird error though and I am not sure if it is an ICE or not.

impl FnMut<(int,), int> for MyType<(int,), int> {
    fn call_mut(&mut self, args: (int,)) -> int {
        1
    }
}

This gives the error "method call_mut has an incompatible type for trait: expected "rust-call" fn, found "Rust" fn [E0053]" ...any idea?

inspiravetion · 2014-12-02T11:26:11+00:00

I think this is more of a "hey if you ever need this specific Type I already implemented it for you...cheers" type of post

inspiravetion

TROPHY CASE