Quim Muntal

Another mishandling: one can skip UNC path normalization by prefixing a UNC path (`host\share`) with `\\?\UNC\`, so `filepath.VolumeName("\\?\UNC\a\b\c")` should return `\\?\UNC\a\b`, not `\\?\UNC`. You can test this in the command...

Hi @anierzad, thanks for submitting this request. I'll think about this during the weekend and report back.

Having a reflection-based API opens the door for an unbounded number of feature requests, as it would never be expressive enough to cover each niche use-case. IMO reading and writing...

Should `CopyFS` also copy symlinks? Something like this: ```go switch m := d.Mode(); { case m.IsRegular(): ... case m&os.ModeSymlink != 0: link, err := os.Readlink(path) if err != nil {...

Hi @husam-e. Thanks for submitting this proposal. What you are asking is already possible using a state machine with external storage: ```go var state State = "A" sm := stateless.NewStateMachineWithExternalStorage(func(_...

> func RemoveIn(parent, name string) error Note that Windows does not provide (AFAIK) an `unlinkat` counterpart. It will have to be emulated doing something like: ```go func RemoveIn(parent, name string)...

There are multiple approaches to support static/dynamic linking, here is mine: - Abstract all `cgo` with an interface that accepts accepts and returns `cgo` types - Do all the gocgo...

I've drafted a working implementation (at least compiling) for the above proposal in https://github.com/qmuntal/AutomaticComponentToolkit/commit/a909c5c55bee45eeb11173c1c2aa37d8e9278cb4, but just the dynamic load implementation.

I don´t think it make sense to add the auto-release capability to the wrapper. It clearly a resource loaded by the user, therefore it should be unloaded by the user,...

> But does that mean the unload will leak memory if the wrapper goes out of scope? Yes, unless the user calls `unload` before the wrapper goes out of scope....