New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace parameter_type == None with parameter_type = {} for non-parametric problems. #84

Closed
sdrave opened this Issue Nov 17, 2014 · 2 comments

Comments

Projects
None yet
2 participants
@sdrave
Member

sdrave commented Nov 17, 2014

Or are there performance impacts?

@sdrave sdrave added this to the 0.4 milestone Nov 17, 2014

@ftalbrecht

This comment has been minimized.

Member

ftalbrecht commented Nov 18, 2014

What kind of usability impacts do you expect (both positive and negative)?

On 17 November 2014 18:04:55 CET, Stephan Rave notifications@github.com wrote:

Or are there performance impacts?


Reply to this email directly or view it on GitHub:
#84

Felix Schindler (born Albrecht)
Applied Mathematics Münster
University of Münster
Orleans-Ring 10, room 120.012
D-48149 Münster, Germany

Tel.: +49 251 83 35130
Fax : +49 251 83 32729
Mail: felix.schindler@wwu.de
WWW: http://felixalbrecht.de

@sdrave

This comment has been minimized.

Member

sdrave commented Mar 3, 2015

Changed in 91558e3. (Regarding usability impacts: The main advantage is that you don't have to different types (NoneType and ParameterType) when looking at the parameter_type of an object.)

@sdrave sdrave closed this Mar 3, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment