Can I make `xPath` and `contextString` private?

# announcements

[Onur]

Can I make xPath and contextString private?

[diesieben07]

No, you cannot lower the visibility of inherited / overridden members. That would violate the liskov substitution principle

[Ruckus]

Even if you were able to mark it as private in ExistingLinkMatch, you could just cast it to Match and access it.

[Onur]

I see, thanks

[Animesh Sahu]

If those variables are defined as val in the Match() interface then you can modify and make them private and can change immutability to var as well.