Geon Kim

@ninedraft LGTM 👍 And, I think we also need more benchmark codes.

Thank you for your proposal. As I commented in another issue, for now, I'm still likely to use `log/slog`. But it is still open to change, so feel free to...

As I commented, `v0.6.0` has been released with `log/slog`. This issue is closed, but feel free to reopen it if you need further discussion about it.

Hi @mbyio! Thank you for your proposal. I'm planning to make some changes to logging in v0.3.0 (using a library like [slog](https://pkg.go.dev/golang.org/x/exp/slog) for structured logging). It won't log everything by...

@thapabishwa-plerionaut I don't know much about the `klog` package. However, I'm currently working on migrating the logging package to `log/slog` (announced in Go 1.21). So, after that, all logs will...

@thapabishwa-plerionaut I am still determining the exact plan, but it is likely to be released either in late November or early December.

@thapabishwa Sorry for being late. The structured logging feature was in private testing, and I just pushed it to the [v0.5.0-pre](https://github.com/KimMachineGun/automemlimit/tree/v0.5.0-pre) branch. (Note: this is not the final version of...

@thapabishwa-plerionaut Thank you for testing! I have just released the pre-release version, and I will release v0.5.0 after a few days of testing. I understand your concerns about updating the...

@thapabishwa-plerionaut Sorry, the testing was done, but it had a tiny issue with its dependency. (https://github.com/containerd/cgroups/pull/321.) Now, the issue is resolved but not released yet. And I'm waiting for the...

@thapabishwa-plerionaut First of all, I feel sorry about it. As @SuperQ mentioned, I decided to delay the release of `log/slog` until the next Go release. Go 1.22 will be released...