Skip to content

Conversation

@hakkelt
Copy link
Contributor

@hakkelt hakkelt commented Nov 27, 2025

Besides removing traits.jl that contained the functions moved to ProximalCore.jl and applying renaming that occurred in ProximalCore.jl v0.2.0, the commit contains the following changes:

Added [workspace] entry to Project.toml. It's a Julia v1.12 feature, ignored by previous versions, that synchronizes versions between subprojects test, docs, and benchmark.

Added traits:

  • is_proximable = true added to SqrNormL2
  • is_positively_homogeneous = true added to SumPositive
  • is_locally_smooth = true added to LogBarrier
  • is_locally_smooth = true added to NormL2

is_locally_smooth(T{W}) = is_locally_smooth(W) added where W is the wrapped function:

  • Postcompose
  • Precompose
  • PrecomposeDiagonal
  • Regularized
  • SeparableSum
  • SlicedSeparableSum
  • Sum
  • Tilt
  • Translate

Implements part of #151

…itable

Besides removing traits.jl that contained the functions moved to ProximalCore.jl
and applying renaming that occured in ProximalCore.jl v0.2.0, the commit contains
the following changes:

Added traits:
- `is_proximable = true` added to `SqrNormL2`
- `is_positively_homogeneous = true` added to `SumPositive`
- `is_locally_smooth = true` added to `LogBarrier`
- `is_locally_smooth = true` added to `NormL2`

`is_locally_smooth(T{W}) = is_locally_smooth(W)` added where W is the wrapped function:
- `Postcompose`
- `Precompose`
- `PrecomposeDiagonal`
- `Regularized`
- `SeparableSum`
- `SlicedSeparableSum`
- `Sum`
- `Tilt`
- `Translate`
lostella
lostella previously approved these changes Dec 25, 2025
@lostella
Copy link
Member

Looks like some docs snippets are failing: https://github.com/JuliaFirstOrder/ProximalOperators.jl/actions/runs/19746713163/job/58926848162?pr=152

Maybe we need to import ProximalCore explicitly in those? I'm wondering what broke them though

@hakkelt
Copy link
Contributor Author

hakkelt commented Dec 30, 2025

Sorry for that -- I fixed it by importing ProximalCore automatically for each snippet (see docs/make.jl). May I also add calling Documenter's doctest to the test suite to catch these mistakes earlier in the future?

Also, tests failed on Julia version 1.6, so I added a commit to replace Julia 1.6 with 1.10 in the test matrix. Is it ok?

@hakkelt hakkelt force-pushed the remove-functions-moved-to-proximalcore branch from f93ef30 to f9ae6dc Compare January 1, 2026 13:03
@hakkelt
Copy link
Contributor Author

hakkelt commented Jan 1, 2026

I reverted the commit that changed the test CI job to use Julia 1.10 instead of 1.6. This is because I realized that there is already a PR to bump Julia version to 1.9 in tests (#149). I tested this PR locally with Julia 1.9, and it works as expected.

lostella
lostella previously approved these changes Jan 1, 2026
@lostella
Copy link
Member

lostella commented Jan 1, 2026

Makes sense, thanks @hakkelt!

@hakkelt
Copy link
Contributor Author

hakkelt commented Jan 6, 2026

My last commit runs doctests as part of the test suite, as discussed earlier.
@lostella, could you please merge this PR or grant me permission to merge approved PRs?

@lostella lostella enabled auto-merge (squash) January 6, 2026 23:02
@lostella lostella merged commit f40159f into JuliaFirstOrder:master Jan 6, 2026
4 of 8 checks passed
@lostella
Copy link
Member

lostella commented Jan 8, 2026

@hakkelt I guess we should also bump to 0.17 before release

@hakkelt
Copy link
Contributor Author

hakkelt commented Jan 8, 2026

I don't see any reason why not.

@hakkelt
Copy link
Contributor Author

hakkelt commented Jan 8, 2026

Is #149 ready to be merged? I saw that this PR also bumps version number?

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