# FixFunctionArgument.jl: Fix a function positional argument to a callable. Stand-in replacement for Base.Fix

**URL:** https://discourse.julialang.org/t/fixfunctionargument-jl-fix-a-function-positional-argument-to-a-callable-stand-in-replacement-for-base-fix/132532
**Category:** Package Announcements
**Tags:** package, announcement, function, functional
**Created:** [September 21, 2025, 7:45am UTC](https://discourse.julialang.org/t/fixfunctionargument-jl-fix-a-function-positional-argument-to-a-callable-stand-in-replacement-for-base-fix/132532 "2025-09-21T07:45:42Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![nsajko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsajko/32/221187_2.png) [@nsajko](https://discourse.julialang.org/u/nsajko)
#### Post date: [September 21, 2025, 7:45am UTC](https://discourse.julialang.org/t/fixfunctionargument-jl-fix-a-function-positional-argument-to-a-callable-stand-in-replacement-for-base-fix/132532/1 "2025-09-21T07:45:42Z")

</div>

Suboptimal design in `Base.Fix`, also applying to `Base.Fix1` and `Base.Fix2`, causes things like `Base.Fix1(convert, Bool)` to have a greater than zero representation in memory, because `Bool isa Type`. Fixing this in `Base` would be arguably breaking, so here’s a new package providing a stand-in replacement to `Base.Fix`, `Base.Fix1`, `Base.Fix2`. The design is meant to be a straight improvement over `Base.Fix`, without unnecessary changes.

- [GitHub - JuliaFunctional/FixFunctionArgument.jl: Fix a function positional argument to a callable. Stand-in replacement for `Base.Fix`.](https://github.com/JuliaFunctional/FixFunctionArgument.jl)

The package has now entered the three-day waiting period, after which it can be registered.

Here’s also the relevant issue ticket on Github:

- [suboptimal design of `Fix`, `ComposedFunction`, `Returns`, `Splat`: `sizeof(Base.Fix1(convert, Float32)) \> 0` · Issue #59619 · JuliaLang/julia · GitHub](https://github.com/JuliaLang/julia/issues/59619)

Update:

- I realized the same issue as with `Base.Fix` is also present with `Returns`, `ComposedFunction` and `Base.Splat`.

- I made a PR which attempts to fix the issues in `Base`:

- The registration of the package is on hold until the PR is resolved. Furthermore, if the PR does not get accepted, the design of the package(s) may be adjusted, as I came to some realizations in the mean time.