-
Hello there!
im currently using something like this in my project (please ignore the specifics, i want to share the general idea without ripping it out of the context that sparked the idea):
```rustโฆ
-
### Describe the feature you'd like:
Happy to give this a try myself!
I've found myself repeating the same pattern of typecasting elements returned from queries when using `render` when I need tโฆ
-
First of all thank you for such a great project. I really like it ๐
I was playing around generic function and found that this code show the error:
```ts
function id(x: T): T {
return x
}
โฆ
-
One thing we don't handle is functions like this:
``` rust
fn dropit(x: T) { }
```
Since we just check all functions, but not instantiations of them, we can call dropit on a drop protected var. Any โฆ
-
I was just mentioning `methods(class = class(.))` in an [e-mail advice on R-help](https://stat.ethz.ch/pipermail/r-help/2024-September/479917.html).
I've advertized this in my intermediate-to-advanโฆ
-
> ## generic type
> * ๋ณดํต ํด๋์ค๋ ์ธํฐํ์ด์ค, ๋ฉ์๋๋ฅผ ์ฌ์ฉํ ๋ ๋์ผํ ๊ธฐ๋ฅ์ ์ํํ์ง๋ง, ์
๋ ฅํ๋ ๋ฐ์ดํฐ ํ์๋ง ํ๋ฆฐ ๊ฒฝ์ฐ
> * ํ์ ํด๋์ค์์ ์์ํด์ ์ถ๊ฐ์ ์ธ ๊ธฐ๋ฅ ์ถ๊ฐ ๋ฐ virtual ํ์ ์๊ฐ ๋ฌ๋ฆฐ ๊ฒ์ ์ฌ์ ์ํด์ ์ฌ์ฉ ๊ฐ๋ฅ
![image](https://user-images.githubusercontent.coโฆ
-
### The following program `sample.go` triggers an unexpected result
```go
package main
import "fmt"
var values = []string{
"hello",
"there",
}
func print[T any](v ...[]T) โฆ
-
As commented in PR #117, would be nice to have some generic input sanitisation functions to call that are centrally managed, and then implemented bot wide. This would ensure that all sanitisation is cโฆ
-
Common Rust wisdom says that `#[inline]` does not need to be placed on small generic functions. This is because generic functions will get monomorphized in each crate anyway, so the attribute is not nโฆ
nikic updated
11 months ago
-
```rust
trait Trait {
fn fun();
}
fn takes_static_fn(_: impl Fn() + 'static) {}
fn test() {
// these work
takes_static_fn(|| T::fun());
takes_static_fn(T::fun as fn());
โฆ