# \#compile-time

**URL:** https://discourse.julialang.org/tag/compile-time/1661.md

[Latest](https://discourse.julialang.org/latest.md) · [Categories](https://discourse.julialang.org/categories.md) · [Tags](https://discourse.julialang.org/tags.md)

---

## [Can I get away with memoizing a :foldable method?](https://discourse.julialang.org/t/can-i-get-away-with-memoizing-a-foldable-method/136951)

<div class="topic-metadata">

**Author:** [@Benny](https://discourse.julialang.org/u/Benny)\
**Replies:** 0\
**Last updated:** [May 1, 2026, 3:48pm UTC](https://discourse.julialang.org/t/can-i-get-away-with-memoizing-a-foldable-method/136951 "2026-05-01T15:48:59Z")

</div>

Starting to dabble in moving long calls from runtime into compile-time, and I’m finding that repeated calls in compile-time are also annoying. Naively, I tried compile-time memoization, also avoiding cache access overhea…

---

## [Timing compilation when using threads](https://discourse.julialang.org/t/timing-compilation-when-using-threads/121001)

<div class="topic-metadata">

**Author:** [@theogf](https://discourse.julialang.org/u/theogf)\
**Replies:** 0\
**Last updated:** [October 7, 2024, 11:56am UTC](https://discourse.julialang.org/t/timing-compilation-when-using-threads/121001 "2024-10-07T11:56:38Z")

</div>

Is it possible to correctly measure compilation time when using Tasks on separate threads? I have tried using the 1.11 @timed but get inconsistent timings for the compilation time. I also don’t have a clear picture of …

---

## [Can \`parse\` be computed at compile time?](https://discourse.julialang.org/t/can-parse-be-computed-at-compile-time/119507)

<div class="topic-metadata">

**Author:** [@greatpet](https://discourse.julialang.org/u/greatpet)\
**Replies:** 4\
**Last updated:** [September 17, 2024, 9:21pm UTC](https://discourse.julialang.org/t/can-parse-be-computed-at-compile-time/119507 "2024-09-17T21:21:13Z")

</div>

The function f() = parse(Int, "10") produces native code, according to @code\_native, which involves runtime parsing rather than directly returning the integer 10. Why can’t Julia optimize this away at compile time? Is…