|
|
178.
|
|
|
`{0}': Base class `{1}' must be specified as first
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1203
|
|
|
179.
|
|
|
Partial declarations of `{0}' must not specify different base classes
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1531
|
|
|
180.
|
|
|
The operator `{0}' requires a matching operator `{1}' to also be defined
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1264
|
|
|
181.
|
|
|
`{0}' clashes with a predefined namespace
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1021
|
|
|
182.
|
|
|
Inherited interface `{0}' causes a cycle in the interface hierarchy of `{1}'
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1583
|
|
|
183.
|
|
|
Circular base class dependency involving `{0}' and `{1}'
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1590
|
|
|
184.
|
|
|
`{0}' cannot implement both `{1}' and `{2}' because they may unify for some type parameter substitutions
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1927
|
|
|
185.
|
|
|
The type `{0}' is defined in an assembly that is not referenced. Consider adding a reference to assembly `{1}'
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:1223
|
|
|
186.
|
|
|
Partial declarations of `{0}' must have the same type parameter names in the same order
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:157
|
|
|
187.
|
|
|
Partial declarations of `{0}' must have the same type parameter variance modifiers
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
mcs/mcs/class.cs:164
|
