
Is there a reason that EnumMap specifically requires containers < 0.3 or just a matter of not having been tested? It seems to compile just fine (but with one warning for a deprecated call). Max

On 12 July 2010 13:04, Max Cantor
Is there a reason that EnumMap specifically requires containers < 0.3 or just a matter of not having been tested? It seems to compile just fine (but with one warning for a deprecated call).
Because it hasn't been updated since containers-0.3 came out, and most programmers don't have crystal balls to be able to see in the future and see if their code will work with future versions of their dependencies. -- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com IvanMiljenovic.wordpress.com

Wasn't implying that they should. My bad for not checking the relative release dates, but, even had I checked, its still reasonable to ask if there are known issues, isn't it? Max On Jul 12, 2010, at 11:06 AM, Ivan Miljenovic wrote:
On 12 July 2010 13:04, Max Cantor
wrote: Is there a reason that EnumMap specifically requires containers < 0.3 or just a matter of not having been tested? It seems to compile just fine (but with one warning for a deprecated call).
Because it hasn't been updated since containers-0.3 came out, and most programmers don't have crystal balls to be able to see in the future and see if their code will work with future versions of their dependencies.
-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com IvanMiljenovic.wordpress.com
participants (2)
-
Ivan Miljenovic
-
Max Cantor