yozu

@clarfonthey I think there's some needs to implement Fn* traits for arbitrary types. 1. Giving multiple function signatures to an object. 2. In following URL, there's some difficulty defining trait...

@bjorn3 Thanks for replying. > we shouldn't support in the first place > preventing multiple impls of Fn* Do you have any standings for preventing higher-order signaitures as mentioned below?...

@zseri > What we really want to prevent here are functions with multiple simultaneous argument counts Is this really harmful? it looks fine in current unstabilized `fn-traits`: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=157729b98808b439ecc992e4ba59273e

@bjorn3 Thanks very much, but I cannot understand the difference of *higher-order function arguments* and *arbitrary function signatures*(function overloading) clearly. Thinking of this example, what is the main factor to...

@bjorn3 If so, the following is different signatures? ```rs fn f(t: T) { unimplemented!() } f("hello"); f("hello".to_owned()); f(vec![1,2,3]); ```

Thanks for reply. I am considering following situations. - Using multiple devices (for example, note pc and desktop pc) - I want to manage local repos, which I am working...

I think working directly on `~/ghq/` is enough considerable, but someone may have different opinions. If there is any other way (or reason why this example is unsound), please let...

today `--shallow` option is usable for this purpose.

related: https://twitter.com/yasuo_ozu/status/1439587987650580480

Thanks for replaying. From my standings, I want to replace `use-image-by-width` with `use-image-by-natural-size` (= `use-image`), because `use-image-by-width` too respects image width (than height) so I think it is irrational. So...