Mak Nazečić-Andrlon

Definitely an issue here.

Hmm, this seems to be tied to the `id` attribute. Two models seems only seem to be considered same if they have the same `id`.

Hmm, that's awkward. So what should I do if my data is just... data? Just give them arbitrary different ids?

I suppose there are two parts here: 1. The metadata should probably indicate that `ID3D11DeviceContext::OMSetRenderTargets()` expects an array of non-null pointers. 2. Input-only array parameters should probably be translated as...

Sort of, but also including the methods currently accessible through the module interface like: ``` client = Etsy::Client.new(:api_key => 'key', :secret => 'secret', :environment => :production) client.user('littletjane') ```

Just as a note, the LLVM LangRef does not currently actually specify that floating-point operations obey IEEE 754 (https://github.com/llvm/llvm-project/issues/60942). Should this be mentioned in the RFC?

> ...Though based on these [StackOverflow](https://stackoverflow.com/questions/2247447/usefulness-of-signaling-nan) [posts](https://stackoverflow.com/questions/3615724/how-to-trace-a-nan-in-c/3616017#3616017) it appears what I want is actually an equivalent to C's `feenableexcept(FE_DIVBYZERO|FE_INVALID|FE_OVERFLOW)`; this would raise an exception on any operation I might want...

What do you mean by "preserve"? We do promise that signs are preserved under copies. The underspecification is in terms of what the sign of a freshly generated NaN is....

Unfortunate that #2233 had to be reverted. Currently I have to use `OMSetRenderTargets` like so: ```rust self.context.OMSetRenderTargets(Some(&[Some(self.render_target_view.clone())]), None) ``` In addition to it being quite ugly, the signature currently forces...

Any updates on this?