# Blog post: Review of trimming for AoC 2025

**URL:** <https://discourse.julialang.org/t/blog-post-review-of-trimming-for-aoc-2025/134384>\
**Category:** Community\
**Created:** [December 5, 2025, 7:29pm UTC](https://discourse.julialang.org/t/blog-post-review-of-trimming-for-aoc-2025/134384 "2025-12-05T19:29:36Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![frankwswang](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/frankwswang/32/18561_2.png) [@frankwswang](https://discourse.julialang.org/u/frankwswang)\
**Post date:** [December 9, 2025, 5:50pm UTC](https://discourse.julialang.org/t/blog-post-review-of-trimming-for-aoc-2025/134384/18 "2025-12-09T17:50:12Z")

</div>

Sounds like this:

> [@Manual control of overloading existing methods](https://discourse.julialang.org/t/manual-control-of-overloading-existing-methods/133836):
>
> I am curious to know how much people want to have a feature/mechanism in Julia to manually control function overloading. Specifically, to disallow overloading already defined methods when intended. One direct motivation for such a restriction is to prevent malicious/unwanted code injection. Consider the following example: julia\> import Base: + # First line after a freshly started Julia REPL julia\> +(::Int, ::Int) = zero(Int) # DANGEROUS!!! Executing the second line of code will cause the Jul…

---

_[View the full topic](https://discourse.julialang.org/t/blog-post-review-of-trimming-for-aoc-2025/134384)._