KIMURA Masaru

FYI, if you don't care portability, you can use foreign attributes like issue #51.

i tried to regenerate `db1` to `db38` coefficients by `boost::multiprecision + eigen3` and it looks good. please see following attached image and linked gist for detail. any chance to make...

investigating `sym2` to `sym20` too. [cmp_sym.m](https://gist.github.com/hiyuh/875d06e046643c6dd7681dee61d45d84) 

@nholighaus ack and yw. @susnak ok. but could you mind to leave runtime computing code for reference as i mentioned as "hybrid"? b/c the code is rare to me.

long time no see. investigating `sym*` is slowly reactivated on my `sym` branch. after reorganize `wfilt_sym.m`, estimated bit accuracy is now varied a bit from `master`, but doesn't looks so...

i'm disapointed that there is no new release yet; i mean no NuGet update. even @alinpahontu2912 said "publish soon" but it already passed over 1 month after his post. needless...

FYI, based on my understanding about PyTorch 2.5.1 + TorchSharp 0.105.0, * frozen `torch.jit.ScriptModule` is loadble through PyTorch `torch.jit.script` - PyTorch `torch.jit.freeze` - PyTorch `torch.jit.save` - TorchSharp `torch.jit.load`. + however,...

* FYI, let me share some my findings which are not covered by changes in this current MR, but related to missing `TorchSharp.Scalar.Dispose`. + TorchSharp `torch.Tensor.add_` may internally call another...

* IMHO, relying implict conversions to type inherits `IDisposable` (i mean `TorchSharp.Scalar`) inside TorchSharp easily produces serious memory leak that won't be able to workaround by user side. * most...

@ds5678 thanks. i'm grandually moving my task from "avoiding memory leak in my app code" to "fix leak in TorchSharp". i'll let you know if my outcome does make something...