You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few things that causes the the code to get all wonky with CodeMirror and some new stuff missing.
The following are some things I've found so far:
// Nested generic types break the highlighting inside the function blockfnfoo(&self,bar:str) -> S<T<Q>>{let x = 2;let y = some.func(&bar);}
// the grammar is not liking the () around procspawn(proc(){let x = 12;// the code inside proc is not parsed correctly and breaks the rest});
letmut x = 2;// it doesn't know mut is a keyword not pat of the name
fndrop(&mutself){// &mut is a keyword too}
match x {// match is not being treated as a keyword}
pubfnfoo(){}// access modifiers are absent from the grammar
#[unstable]// we might want to treat this #[] as a special thingpubfnfoo() -> (){}
// 'static is a keyword toopubfnfoo() -> &'staticT{}
// not sure why, but this reads better in github.// They all get ignored until the last call before the (), // it's very easy to identify what you are calling without getting lost
some.func.call(&bar);
// this is another case where it reads more clear in Github, // with the current CodeMirror it all comes out in the same colorOk(foo.bar);Err(foo.bar.call());
// I would place mut, &, &mut, ref and * (deref) // on their own little group
I noticed @marijnh did the initial contribution and maintained it over the years.
Can you help update the language definition?
There are a few things that causes the the code to get all wonky with CodeMirror and some new stuff missing.
The following are some things I've found so far:
I noticed @marijnh did the initial contribution and maintained it over the years.
Can you help update the language definition?