[Dune] [#1094] Compiling Generic Reference Elements Requires too much Memory

Dune flyspray at dune-project.org
Thu May 3 23:07:19 CEST 2012


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#1094 - Compiling Generic Reference Elements Requires too much Memory
User who did this - Oliver Sander (sander)

----------
Hi Martin,
I want to apologize for the wording of my last post.  It was rude and I shouldn't have written it that way.  However, I do stick to my point.  I do not really know whether your patch is a good idea, but I tend to think that it is useful.  But that is not the point.  The point is that this issue here is for a fairly exotic problem (few people do dim>3), nobody knew about this one week ago, and yet here we are being asked to do an interface change as soon as possible.  I just don't think that's the way how you to write professional-grade libraries once your userbase exceeds a certain threshold.  How often does MPI add new features?  They think about these things for years before adding stuff to the API.

Related: I have heard the argument 'I need to have feature XYZ in the trunk right away, because I can't use branches' quite a few times recently.  Let's move over to git then, so the trunk can stay stable and people that need to experiment with features can do that comfortably in branches.

Oliver

----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1094#comment3478

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.




More information about the Dune mailing list