Some thoughts on the Interface Default Methods RFC

• Symfony

  151 29,325 10.0 PHP

  The Symfony PHP framework

  

OK, bad example. The more realistic is this one. It did change over the years but because users are extending AbstractType, that wasn't a big deal.

• BackwardCompatibilityCheck

  3 559 8.3 PHP

  :ab: Tool to compare two revisions of a class API to check for BC breaks

  

It's also not a big risk because if it does fail it will fail every time you just load the class that implements the interface so probably your while site will error. If you do cursory testing of the new version before you deploy it you can find the problem quickly before it becomes a problem. You can also do static analysis checks on your code to make sure its compatible with the libraries you use including when you upgrade them. And library maintainers can run Roave/BackwardCompatibilityCheck/ to make sure they don't accidentally introduce a new interface method without declaring a new major version.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project