Skip to content
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

Accept multidimensional arrays as input #55

Merged
merged 2 commits into from
Jun 25, 2017
Merged

Accept multidimensional arrays as input #55

merged 2 commits into from
Jun 25, 2017

Conversation

antoine-levitt
Copy link
Contributor

Simple vector->array. I also typed everything to T for consistency.

@codecov
Copy link

codecov bot commented Jun 25, 2017

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #55   +/-   ##
=======================================
  Coverage   62.81%   62.81%           
=======================================
  Files           8        8           
  Lines         589      589           
=======================================
  Hits          370      370           
  Misses        219      219
Impacted Files Coverage Δ
src/basic.jl 100% <ø> (ø) ⬆️
src/hagerzhang.jl 62.01% <ø> (ø) ⬆️
src/strongwolfe.jl 90% <ø> (ø) ⬆️
src/morethuente.jl 68.57% <ø> (ø) ⬆️
src/backtracking.jl 94.28% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 32f5337...468f40f. Read the comment docs.

@anriseth
Copy link
Collaborator

anriseth commented Jun 25, 2017

Thank you for improving all the obsolete overtyping @antoine-levitt :)
Is there a reason for why we are stopping at Array? (EDIT: as opposed to something more abstract)

@antoine-levitt
Copy link
Contributor Author

Not sure, that depends on whether concrete types in structs are important or not. An alternative is to force static typing by using parametric types, but there must be a downside to doing that and just parametrizing the type of every field in a struct, otherwise why would anybody ever do anything else?

@anriseth
Copy link
Collaborator

anriseth commented Jun 25, 2017 via email

@antoine-levitt
Copy link
Contributor Author

The API is wrong in any case, because linesearch should only see, well, line searches and the API should be rewritten, so this conversation is best had at the Optim level (see JuliaNLSolvers/Optim.jl#399)

@anriseth anriseth merged commit f382f9c into JuliaNLSolvers:master Jun 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants