hexane360

>introduce an actually memory safe (unlike borrow checking) compilation mode inspired by Fil-C

I've also played around with writing my own dataclass/data conversion library: https://github.com/hexane360/pane

Libraries like BOSL2 help with placement/attachment of features: https://github.com/BelfrySCAD/BOSL2

Reagan did it with a single phone call: https://www.nytimes.com/1982/08/13/world/reagan-demands-end-...

As a concrete example, consider a map with a method get(key: K) -> Option<V>. How do you tell the difference between a missing key and a key which contains `null` as a value?

Here's the full quote:

"While it is never safe to affirm that the future of Physical Science has no marvels in store even more astonishing than those of the past, it seems probable that most of the grand underlying principles have been firmly established and that further advances are to be sought chiefly in the rigorous application of these principles to all the phenomena which come under our notice. It is here that the science of measurement shows its importance — where quantitative work is more to be desired than qualitative work. An eminent physicist remarked that the future truths of physical science are to be looked for in the sixth place of decimals."

At least they support ~=3.9 and >=1,<3 comparisons (although this is undocumented as far as I can tell.

You accuse me of arguing dishonestly. Instead, why don't you present your evidence that MIT has acted against its policy in an official capacity?

If anything, MIT has been more forceful in setting limits on pro-Palestinian demonstrations than on anti-LGBTQ speech.

> "Our enemies are innovative and resourceful, and so are we. They never stop thinking 'bout new ways to harm our country and our people, and neither do we."

> "It was not always a given that the United States and America would have a close relationship"

> "Who could have possibly considered an erection in Iraq at this point in history?"

> "I know the human being and fish can coexist peacefully."

https://numpy.org/neps/nep-0023-backwards-compatibility.html

https://numpy.org/doc/stable/dev/depending_on_numpy.html#run...

So, when using numpy in a package, and you've tested e.g. versions 1.12 to 1.22, you should require 'numpy>=1.12,<1.25', because something deprecated in version 1.23 could be removed in 1.25.

Such macros can be defined by libraries or the end user to provide special behavior.

"Type inference" is what you're referring to, and is an optional feature of static type checkers. For instance, C has static types but no type inference, while C++ has static types with type inference. The concept of "type inference" doesn't make sense for dynamic typing.