core: Comment on why `scan_result` is not deinit-ed I thought it's confusing during refactoring.

Changes

1 changed files (+3/-0)

• core/src/App/ServerSelector.zig
  • @@ -30,6 +30,9 @@ allocator: std.mem.Allocator,
    on_change_callbacks: OnChange.Store, capi_lock: std.Thread.Mutex, has_loaded_once: bool = false, + + /// Acts as backing buffer for `CApi.entries`. For this reason, `CApi` manages this + /// struct's memory. scan_result: ?std.StringHashMap(Entry.CApi) = null, pub fn init(allocator: std.mem.Allocator) Self {