[Dune-devel] Possible removal of method ReferenceElement::checkInside<codim>

[Oliver Sander]

Hi Martin,
thanks for clarifying your point.  Even though I still don't see the value of deprecating this particular
method, I do agree that not rushing API changes is very important.  I have therefore only deprecated the
method for the 2.4 release, and will not touch it until 2.4 is out.
Best,
Oliver

Am 05.07.2015 um 23:09 schrieb Martin Nolte:
> Hi Oli,
> 
> I think we should remain true to our policy on interface changes: Deprecate before removing. In my opinion, you name a very argument in favor of deprecation: Nobody will see the warning, so it will
> annoy nobody.
> 
> But personally, I would have voted differently, if 2.4 had not been on our doorstep. I don't think we should make such aggressive last minute changes.
> 
> Moreover, I think Robert is entitled to an opionion on deprecation or not, too. This is especially so, as his point was overruled.
> 
> That said, I stand by democracy. The majority of non-abstained votes is for throwing out the method now - so be it. However, I guess you have to wait for the pending answers. They might still change
> the outcome.
> 
> Best,
> 
> Martin
> 
> On 07/05/2015 10:56 PM, Oliver Sander wrote:
>>> unless there is no performance penalty or an disproportional amount
>>> of work, I would never remove a feature without deprecation.
>>
>> But who will see this particular deprecation warning?
>>
>>
>>
>>
>> _______________________________________________
>> Dune-devel mailing list
>> Dune-devel at dune-project.org
>> http://lists.dune-project.org/mailman/listinfo/dune-devel
>>
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20150706/a9034518/attachment.sig>