444 karma · joined October 13, 2013
https://wickedengine.net/2018/05/21/scalabe-gpu-fluid-simula...
https://developer.nvidia.com/gpugems/gpugems3/part-i-geometr...
In Haskell, you can omit these fields entirely, and achieve the same thing just by annotating the function.
For example, in Haskell, we can have
data Const a b = Const a
whereas in Rust, it would be: struct Const<A, B> {
konst: A,
// does not exist at run-time
discard: PhantomData<B>
}Nice to see something like this in Rust! One thing that's a bit of a bummer, and I'm sure there are very good reasons for this, is that we HAVE to use every type argument of struct in its definition. If this restriction were to be relaxed, we wouldn't need the "state" field in the struct at all, and we could make the state type variable truly "phantom".
[1] https://www.schoolofhaskell.com/user/konn/prove-your-haskell...
EDIT: Typos.
Organizations setting limits on what type of discussion is allowed is a good thing, and again, specifics matter. The statement, at its heart, stifles the speech of these groups by trivializing the concerns of those people who are affected by the systems termed "rape culture"( systems supporting violence against certain groups ). The fact that the transition to a more inclusive community involves prohibiting this type of speech is a given IMO, since that speech is precisely what makes for a hostile climate to non-white-guy contributors. Such statements are problematic if the community in question claims to be based on freedom and inclusivity.
[Edit]: In general, I think "freedom of speech"( and the implied "freedom to be offended" ), are less important than maintaining a community climate that feels safe for its members.
I think a lot of good would come if we stopped using the word "censorship", and just responded to what people actually had concerns with. Censorship is distinct from a dude stating his opinions, and encouraging others to agree with him.
(Edit): * defending nuanced discussion about the value of rape culture as a concept