Hacker News new | past | comments | ask | show | jobs | submit | more mbnull's comments login


unless errorlevel is exported as ErrorLevel you can only do so inside the declaring package.


Indeed, that was the idea behind keeping it unexported.

From an external package you can only access the explicit values and the functions that accept them as parameters. The type is opaque for the developer.


Yeah, ok, fair point. That kinda works, but enums would be better


Occam's Razor postulates that the simple solution is often the right one. That does not mean it's always so. For the longest time Occam's Razor would have favored a flat earth, before we knew better.

Alien intelligence would also be alien enough if it wasn't interstellar. Interplanetary, inter-dimensional or subterranean would be alien by my standard, too.

The Videos might have been plausibly explained, but i would argue that the pentagon has certainly more footage and sensor data to base their statement on.

And please do try to take photos of planes in the night sky with your smartphone camera. The image quality is not great.


There is nothing "simple" about the concept of flat earth. It's one set of exceptions on top of another set of exceptions, ad infinitum.

To use the pre-enlightenment list of exceptions: It's flat, but not infinite. It's a disc. Ringed by mountains. Held up by giant elephants. On the back of a turtle. On the back of another turtle.

The modern "rationale" for flat earth is just as complex (not simple) an explanation of exceptions upon exceptions. The Copernican, Galileo-an and Newtonian attempts to explain things are much closer to "simple", despite being incomplete, because they are experimentally gathered and predictive and not just mentally created from whole cloth.


Medieval people did not think the Earth was flat.

https://en.wikipedia.org/wiki/Myth_of_the_flat_Earth


Medieval people certainly believed that. The linked wikipedia page does not say otherwise. It states that "European scholars and educated people during the Middle Ages believed the Earth to be flat". Most people in Medieval times were not scholars or educated. Furthermore I haven't even said anything about Medieval times.

There are other examples like rocks falling from the sky or the earth- or solar-centric cosmos, if you prefer.


That Wikipedia page can be edited by any visitor, therefore it is not a reliable authority on the posted information. Take a look at the revision history page for your link, https://en.wikipedia.org/w/index.php?title=Myth_of_the_flat_.... Half of the edits appear not to be attributed to people but to unnamed ip addresses.

i.e. Don't believe everything you read.

To illustrate this point, go to different Wikipedia page that shows the opposite of what you wrote, https://en.wikipedia.org/wiki/Flat_Earth and look at the Early Middle Ages of Europe, https://en.wikipedia.org/wiki/Flat_Earth#Europe:_Early_Middl....


"Occam's Razor postulates that the simple solution is often the right one. That does not mean it's always so. For the longest time Occam's Razor would have favored a flat earth, before we knew better."

Actually this is problem with the simplifying Occam's Razor. It is not about simple solution, it is about fewer assumptions. Actually with each assumption you are limiting the domain of the question.

Actually before we observed more (like before we knew better), earth being flat is the correct solution vs earth being round.


AFAIK the plant produces more resin, and some compounds therein, to protect itself from the suns UVB radiation.


Where can I read more on this?


I found this paper from 1987 https://sci-hub.se/https://doi.org/10.1111/j.1751-1097.1987....

You will also find lots of experience reports and discussions of appropriate light sources on numerous grower sites.


It uses effectively only the one keyword assure. The constraints look like fields on the type variables, which have an ambiguity with package private method expressions with the same name.


The constraint expressions are expected to be used in generic declaration body scopes instead of top package scopes. For example: https://github.com/dotaheor/unify-Go-builtin-and-custom-gene..., so I think the ambiguity should not happen.


I would prefer naming that feels less procedural. I think of it like a guard so maybe `when` or `where`. It can also just be some punctuation like `| cond` `| another-cond`.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: