1,296 karma · joined December 2, 2019
I also like compost.
and radio.
blog.cofree.coffee www.kpbj.fm www.kchungradio.org
ssbothwell_at_gmail_dot_com
It is orders of magnitude better then Haskell where the best you can do is hacky bullshit with singletons, GADTs, and type families.
That said there are other languages such as Agda, Idris, and Rocq that would be fantastic replacements to Lean, especially if you care about staying constructive.
1. https://homepages.inf.ed.ac.uk/slindley/papers/hasochism.pdf
I deeply wish I had time to do it again.
https://hackage-content.haskell.org/package/base-4.22.0.0/do...
Its a wrapper around an `Integer` where you declare the scale in the type. So if you use `Fixed E2` as your type then `MkFixed 1` is 1 cent. If you did `Fixed E3` as your type then `MkFixed 1` is 0.1 cent. In both cases it is entirely an integer encoding.
There is probably a bunch of subtlety about where you measure from as your antenna could be quite large.
The Part15 regulations for AM and FM are more subtle then what you present here. On FM it is based on field strength readings, the exact values of which escape me, but yielding roughly the range you describe.
For AM the rules are more interesting. You can have up to a 3m antenna length and 100mW of DC power input to the final stage of amplification. The optimal setup is a class E amplifier with ~95-99% efficiency into a properly grounded 3m base loaded vertical antenna. The antenna will be grossly undersized but you try to compensate with a huge loading coil. In ideal conditions this setup can get you about 0.5km range.
LPFM is a much more significant undertaking and it is not trivial to get an LPFM license. I know because I have one :)
There are many more LFPMs out there too!
Imagine someone honestly interested in learning about category theory but not yet knowing where to start. Projects like this only serve to muddy the waters obscuring paths to actual learning and giving the impression that the subject is a joke.
The student is mid learning process and its entirely reasonable for them one to be relying on pattern recognition until they have fully internalized the subject. The model is fully trained and should thus have internalized their understanding of the subject.
Additionally the student can update their understanding when pattern recognition fails. The model is fully cooked and will never do more then pattern recognition.
newtype Mealy s i o = Mealy { runMealy :: (s, i) -> (s, o) }
And it gave a really impressive analysis.Then I scrambled all the names and asked with a fresh context like:
newtype Foo z e g = Bar { blob :: (z, e) -> (z, g) }
It got completely confused and generated a bunch of non-sense. It was at that moment I realized that LLMs don't really understand anything.And yes I understand that a newer model would not get confused by this.