OffsetArrays.jl
AoC
OffsetArrays.jl | AoC | |
---|---|---|
7 | 87 | |
192 | 18 | |
1.0% | - | |
6.0 | 8.1 | |
18 days ago | 5 days ago | |
Julia | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
OffsetArrays.jl
-
Why I am switching my programming language to 1-based array indexing.
Well, there is OffsetArrays in Julia, but it has acquired a reputation as a poison pill because most code assumes the 1-based indexing and it's easy to forget to convert the indexing and screw up the code.
-
The Julia language has a number of correctness flaws
Similar correctness issues are a big part of the reason that, several years ago, I submitted a series of pull requests to Julia so that its entire test suite would run without memory errors under Valgrind, save for a few that either (i) we understood and wrote suppressions for, or (ii) we did not understand and had open issues for. Unfortunately, no one ever integrated Valgrind into the CI system, so the test suite no longer fully runs under it, last time I checked. (The test suite took nearly a day to run under Valgrind on a fast desktop machine when it worked, so is infeasible for every pull request, but could be done periodically, e.g. once every few days.)
Even a revived effort on getting core Julia tests to pass under Valgrind would not do much to help catch correctness bugs due to composing different packages in the ecosystem. For that, running in testing with `--check-bounds=yes` is probably a better solution, and much quicker to execute as well. (see e.g. https://github.com/JuliaArrays/OffsetArrays.jl/issues/282)
-
-🎄- 2021 Day 6 Solutions -🎄-
You might be interested in OffsetArrays.jl.
- PyTorch: Where we are headed and why it looks a lot like Julia (but not exactly)
-
Why does Julia adopt 1-based index?
Counting starts at one, as do most vector/matrix/tensor indices. If it bothers you too much, see OffsetArrays.jl and Arrays with custom indices.
- some may hate it, some may love it
-
Evcxr: A Rust REPL and Jupyter Kernel
No need for another version, Julia supports custom indices by default. Check out https://docs.julialang.org/en/v1/devdocs/offset-arrays/ and https://github.com/JuliaArrays/OffsetArrays.jl
AoC
-
-❄️- 2023 Day 11 Solutions -❄️-
20ms both parts https://github.com/Fadi88/AoC/blob/master/2023/day11/code.py
- -❄️- 2023 Day 9 Solutions -❄️-
- -❄️- 2023 Day 8 Solutions -❄️-
- -❄️- 2023 Day 7 Solutions -❄️-
-
-❄️- 2023 Day 6 Solutions -❄️-
Same Algo as my python code from earlier, now just using math not search space reduction also blazing fast in micro seconds https://github.com/Fadi88/AoC/tree/master/2023/day06
- -❄️- 2023 Day 5 Solutions -❄️-
- [2022-day16] python port to rust performance question
- -🎄- 2022 Day 25 Solutions -🎄-
- -🎄- 2022 Day 24 Solutions -🎄-
- -🎄- 2022 Day 23 Solutions -🎄-
What are some alternatives?
StarWarsArrays.jl - Arrays indexed as the order of Star Wars movies
advent-of-code - My solutions for Advent of Code
TwoBasedIndexing.jl - Two-based indexing
adventofcode - Solutions for problems from AdventOfCode.com
Optimization.jl - Mathematical Optimization in Julia. Local, global, gradient-based and derivative-free. Linear, Quadratic, Convex, Mixed-Integer, and Nonlinear Optimization in one simple, fast, and differentiable interface.
aoc2020 - Advent of Code 2020 - my answers
TailRec.jl - A tail recursion optimization macro for julia.
AdventOfCode-Java - adventOfCode(Language.JAVA);
julia - The Julia Programming Language
advent-of-code-go - All 8 years of adventofcode.com solutions in Go/Golang; 2015 2016 2017 2018 2019 2020 2021 2022
StatsBase.jl - Basic statistics for Julia
aoc2021 - Advent of Code 2021 Solutions