Scratch allocator for filepath.walk instead of context.temp_allocator

[nkxxll]

This is a thing that tripped me hard. Think of it that way a temp_allocator is for when you have a scoped thing and don't want to think about memory in this scoped thing. Now you walk the file tree and use the temp_allocator for a file as scope... then everything falls apart and the tree traversal does not work (fails silently).

Wouldn't it be more intuitive to use a scratch allocator for the internal functions not the temp_allocator that might be used by the developer.

Disclaimer: I am new to odin this could be a skill issue, if so then tell me I'll back off, in tremendous shame ;D

code example:

err := filepath.walk(".", walk, nil)
...
walk :: proc(...) -> (...) {
    defer free_all(context.temp_allocator)

    // cool formatted filename output that has to be allocated representative for any
    // temporary data that might have to be allocated here
    cool_filename := fmt.tprintf("full: %v, name: %v\n", info.fullname, info.name)
    fmt.println(cool_filename)
    return nil, false
}

this goes to shambles...