[250] Issues with generic type parameter + constraints at operation level

I don't know if this has been reported already by someone else but there are two issues concerning type parameter constraints in operations.

1.
The first issue is not really a big but it depends on how you look at it. In the ReSharper options under Code Style -> C# -> Line Breaks and Wrappers there are 3 options concerning type parameters, unfortunately these are for type parameters at the class declaration level. With other words type parameters and type parameters constraints declared at operation level are not affected by these options after a code reformat.

2.
The second issue is a bug that occurs when implementing an interface that has type parameter constraints declared at operation level as shown in the example:

1: public TReturnValue Execute<TObject, TReturnValue>(TObject value) where TObject : class where TReturnValue : class 2: When declaring a class that implements the interface ICommand which has a member Execute this is the result (look at the end of line number 1 "classwhere"): 1: public TReturnValue Execute<TObject, TReturnValue>(TObject value) where TObject : classwhere 2: Cheers Gabriel Lozano-Morán

1 comment
Comment actions Permalink

Thank you
Both issues will be fixed shortly

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Gabriel Lozano-Morán" <jb-newsgroups@pointerx.net> wrote in message news:e64dv2$vee$1@is.intellij.net...
I don't know if this has been reported already by someone else but there are two issues concerning type parameter constraints in operations.

1.
The first issue is not really a big but it depends on how you look at it. In the ReSharper options under Code Style -> C# -> Line Breaks and Wrappers there are 3 options concerning type parameters, unfortunately these are for type parameters at the class declaration level. With other words type parameters and type parameters constraints declared at operation level are not affected by these options after a code reformat.

2.
The second issue is a bug that occurs when implementing an interface that has type parameter constraints declared at operation level as shown in the example:

1: public TReturnValue Execute<TObject, TReturnValue>(TObject value) where TObject : class where TReturnValue : class 2: When declaring a class that implements the interface ICommand which has a member Execute this is the result (look at the end of line number 1 "classwhere"): 1: public TReturnValue Execute<TObject, TReturnValue>(TObject value) where TObject : classwhere 2: Cheers Gabriel Lozano-Morán

0

Please sign in to leave a comment.