-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Codist 7.9 beta #316
Comments
I've just upgraded to VS 17.9 and observed that Codist interferes with the default colorization. Disabling Codist will bring back the behaviour. My temporary solution is enabling syntax highlight of Codist. |
@fitdev |
Thank you for the new release! I will try it soon. BTW, I have been using C# 12 for some time now, and have not noticed any issues with Codist C#-wise. Out of curiosity - what was added in this beta version then? Also, regarding syntax highlights being messed up - it happened to me on and off for the last 2 or so years - almost every time I would update VS. I am still on an older VS 17.9 preview for the time being, so I don;t know if the issue would affect me were I to upgrade top their latest 17.10 preview released yesterday. |
Weird, it works now, and I've done nothing. |
The new beta has supported highlight of collection expression, primary constructor of base type and the Quick Info of lambda expression return value. |
Hi, it's acting up again. You can try this solution. It's just a source generator solution and you don't need Unity. After opening the solution in VS, I open this file |
@laicasaane |
Here is the solution: And the recent screen recording: |
For completeness, this is my Codist settings: |
@laicasaane At this moment, you have to enable the Syntax Highlight feature in Codist and try your luck. |
I'm OK with enabling Codist syntax highlight feature atm. However, this happens: #316 (comment) |
@laicasaane |
I deliberately changed the style of |
So does the new behavior extend the previous options to also apply to operators? Previously it was only for "Braces and Parentheses". |
Hi, everybody. There's a new beta which enhances highlight (three more syntax styles for customization) and editing of Markdown documents. |
Which ones are those? |
There is a new test version which addresses VS startup slowdown caused by Codist, reported from the Performance Manager. |
The previous 9788 build could crash VS. Please download the newly uploaded 9798 build. |
Oops, 9808 should fix the crash. |
I am not sure if has worked correctly in Codist before, and perhaps is no longer working now, but there seems to be an issue with "Find Referrers" command for implicit operators. They only seem to find the cases of direct casts, with implict casts not being returned: struct Foo {
public static implicit operator Foo(int i) => new Foo();
}
class Usage {
void Test() {
Foo foo1 = (Foo)25; //This is found
Foo foo2 = 34; //This will not be found
}
} Also there is a slight issue where implicit/explicit operators do not have super quick infos for them, they are only selectable using NaviBar. |
It is a known issue. It never works. You can use the following snippet: struct Foo
{
public static implicit operator Foo(int i) => new Foo();
}
class Usage
{
void Explicit() {
Foo foo1 = (Foo)25; //This is found
}
void Implicit() {
Foo foo2 = 34; //This will not be found
}
} Right click the |
Oh I see - it is a Roslyn issue. Sorry for the comment then. Hopefully they will address it soon. |
@fitdev In short, use implicit conversion sparingly and do not do expensive or complicate works within it. |
I find them extremely useful, especially for "smart" arguments, where the caller may use several different types depending on the need - like an int, or a string, or an enum (in this example for a user-defined TextEncoding type which can be initialized from a set of known encodings, a codepage, and encoding name for example) - all of which get auto-converted to the proper type though these implicit operators. So I wish Roslyn would fix it and allow one to see all instances of implicit conversion taking place. |
It is possible to detect this type of situations in the Find Parameter Assignment function though. Please check whether the detection hurts the performance of that function. |
Thank you for the new beta! I am not sure though if it is of much help in finding implicit operator usages, since typically there would be 10s of methods - all accepting the same "Smart"-Struct-Typed argument with possibly 100s of usages across all these methods. But being able to see such implicit conversion in the Parameter Assignment list is very nice nonetheless, thank you! |
Download
Codist 9886
Codist 9884
Codist 9881
Codist 9869
Codist 9861
Codist 9859
Codist 9848
Codist 9846
Codist 9840
Codist 9838
Codist 9822
Codist 9808
Codist 9743
Codist 9635
Codist 9589
Codist 9584
Codist 9583
Codist 9573
What's New
<see>
and<seealso>
elements in C# XML Documentations (XmlDoc Custom Link Text Not Working For cref in see and seealso #327)The text was updated successfully, but these errors were encountered: