I think I know the answer to this but I have the need to specify that a generic method can take a type based on two optional constraints. That being that T can be either one type or another.
public WebPage Click<T>(Func<WebPage> predicate) where T : LinkBase || FieldBase, new()
{
WebDriver.FindElement(new T().LinkPath).Click();
WebDriver.Wait();
return predicate.Invoke();
}
I know that there is no such syntax currently, but is there a way to solve this without duplicating the method to constrain on both types? If not, is this in the realms of possibility for a future version of the language?
C programming language is a machine-independent programming language that is mainly used to create many types of applications and operating systems such as Windows, and other complicated programs such as the Oracle database, Git, Python interpreter, and games and is considered a programming foundation in the process of ...
In the real sense it has no meaning or full form. It was developed by Dennis Ritchie and Ken Thompson at AT&T bell Lab. First, they used to call it as B language then later they made some improvement into it and renamed it as C and its superscript as C++ which was invented by Dr.
What is C? C is a general-purpose programming language created by Dennis Ritchie at the Bell Laboratories in 1972. It is a very popular language, despite being old. C is strongly associated with UNIX, as it was developed to write the UNIX operating system.
C is a general-purpose language that most programmers learn before moving on to more complex languages. From Unix and Windows to Tic Tac Toe and Photoshop, several of the most commonly used applications today have been built on C. It is easy to learn because: A simple syntax with only 32 keywords.
Doing this does not make sense if LinkBase
and FieldBase
do not have a common base or implement a common interface. And if they do, then you can simply use that one as the constraint.
I 'm saying it does not make sense because the very reason of using type constraints is to make sure that the actual generic type parameter used supports a known public interface (otherwise, you could have just made the whole thing to be non-generic and use object
). But if you have a hypothetical "or" constraint, how would the compiler be able to make sure that the code you write inside the generic will actually be meaningful for the type parameter that ends up being specified?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With