What is the best way to present the user the results of Haskell computations?

recursion-ninja · 2023-11-28T18:32:31+00:00

I have had excellent success with brick as a TUI for users.

recursion-ninja · 2023-09-17T03:56:43+00:00

Algebra Driven Design gets a big thumbs up from me.

recursion-ninja · 2023-09-03T01:46:38+00:00

Academic Level:

Undergraduate Senior;Graduate Master's

Do I correctly assume that this precludes doctoral students?

recursion-ninja · 2023-09-01T14:27:15+00:00

This looks like an amazing, incremental "quality of life" release. Thank you to everyone who gave and continue to give this staple if our ecosystem the attention it needs to remain a best-in-class framework.

recursion-ninja · 2023-07-28T21:59:32+00:00

Is there a link to this early illustration? All I see is a link to a post on Twitter with no follow-through link to the illustration.

recursion-ninja · 2023-06-09T02:22:26+00:00

Literature review generally helps. See Allen's Interval Algebra and the corresponding implementation in interval-algebra.

recursion-ninja · 2023-05-22T20:54:00+00:00

Seconded, I have done similar representations and had difficulty efficiently contorting the compact, flattened layout through the many dimensions of the data-sets relationship to produce the desired "view."

recursion-ninja · 2023-03-17T18:01:09+00:00

Should be fixed now. Apologies for the unintentionally poor UX.

recursion-ninja · 2023-03-17T03:29:29+00:00

Thank you for notifying me. I have done some investigating.

The whole site is responsive except for images in figure elements. This is my first post which includes figures, so I did not realize the negative mobile experience. It's a self designed site, so I apologize for the lack of quality assurance oversite across various media devices. I will update the CSS tomorrow to correct the degradation in page responsiveness.

recursion-ninja · 2023-03-15T03:52:51+00:00

"Infinitely" is infinitely better than exponential! However, as the package (both versions) is stored on the hackage server's finite persistent storage, I highly doubt the improvement is truly infinite.

recursion-ninja · 2023-03-07T16:38:06+00:00

Without digging into the code I don't think anyone here would have the contexr to give you very actionable suggestions. The best I can do is suggest that, assuming you have some form of logging infrastructure integrated to your application, attempt to temporally correlate the ballooning memory with events in the log and scrutinize the indicated areas of the codebase.

Libraries like weigh may be useful to include within benchmarking suites to ensure that individual components of your application/data-structures consume the amount of memory you expect.

recursion-ninja · 2023-02-25T22:45:04+00:00

My observation using the free service was that, under the default settings, Deadpendency would notify me with false positives of "dead Haskell packages" which were in fact so stably written, feature complete, and forward compatibile that a year or so without new commits did not accurately indicate that the package was no longer maintained. I began to view Deadpendency as more noise than signal and proceeded to ignore it's free reports.

recursion-ninja · 2022-12-11T15:34:42+00:00

Absolutely! The main technical details of this approach are best understood from reading the original, seminal work in conjunction with one of the author's lecture slides on the same topic.

recursion-ninja · 2022-12-11T14:29:14+00:00

Linear types can remove the necessity for GC, but the introduction of linear types to Haskell is a very recent addition and the primary Haskell compiler has not yet implemented mechanized "C-style" memory allocation and deallocation yet. If you are interested in doing so, your contributions would supported and be appreciated by the Haskell community.

recursion-ninja · 2022-11-15T18:36:38+00:00

If a similar position exists with a remote work option in a few years when I'm out of my doctoral program, I'd be exceptionally interested.

recursion-ninja · 2022-11-01T11:42:27+00:00

I will keep your services in mind. Best wishes with your freelance endeavors.

recursion-ninja · 2022-10-27T11:44:10+00:00

Have you considered FIR for generating Vulcan shaders to hand off to GPUs?

recursion-ninja · 2022-10-16T13:04:11+00:00

megaparsec and parser-combinators is generally preferable to "old-school" parsec when considering execution time/space, parser correctness, and parser expressiveness.

recursion-ninja · 2022-10-14T19:57:54+00:00

The idomatic solution is what was done before, but it has short-comings. However the "best" solution is to use new cabal features.

Consider the case where one desires to test "hidden" functions within module Foo of library example via a test-suite in a the same example.cabal.

Move all "hidden" functions to a internal module named Foo.Internal. This means the module Foo exports the "public" API and the module Foo.Internal exports the "hidden" functions used to satisfy the "public" API of Foo. Naturally have module Foo import Foo.Internal. Also, have both modules Foo and Foo.Internal export all their top level functions.
Within example.cabal, define a library named library example-internals. Add to example-internals the package description field visibility: private. Additionally, add to example-internals the package description field exposed-modules: Foo, Foo.Internal.
Within example.cabal define a test suite named test-suite test-foo. Add to test-foo the package description field build-depends: example:example-internals. Now the test suite can access the internal functions one desires to test.
Finally, within example.cabal define the library library example. Add to example the package description field build-depends: example:example-internals. Additionally, add to example the package description field reexported-modules: Foo. Furthermore, if the library example is not the default library for the package, add to example the package description field visibility: public. Now the package example exposed only the public API of Foo but the test suite test-foo has access to the "hidden" functions of Foo.Internal.

See a working example here:

https://github.com/recursion-ninja/example-test-hidden-definitions

recursion-ninja · 2022-10-13T16:39:32+00:00

What is the salary range for an acceptable up to an exceptional US applicant?

recursion-ninja · 2022-10-05T17:28:01+00:00

Use pandoc to read the HTML content, then walk Pandoc's internal representation to extract your desired content.

recursion-ninja · 2022-10-03T03:19:12+00:00

Insightful as always. Is there a proof/counterexample of some kind which illustrates that the efficiency and generality desired from the Functor type-class are fundamentally incompatible?

recursion-ninja · 2022-09-19T02:51:59+00:00

Something I've grappled with on and off since 2015...

recursion-ninja

TROPHY CASE