kubukoz

//> using scala 3.7
//> using dep org.http4s::http4s-ember-server:0.23.30
//> using dep org.http4s::http4s-dsl:0.23.30
//> using dep org.http4s::http4s-scalatags::0.25.2
//> using option -Wunused:all
import scalatags.Text.all.*
import cats.effect.*
import fs2.Stream
import org.http4s.*
import org.http4s.dsl.io.*

jakzal

These are code examples for the “Functional event sourcing example in Kotlin” article:

https://zalas.pl/functional-event-sourcing-example-in-kotlin/

All gists:

• Functional event sourcing example in Kotlin

• Deriving state from events

• Object-oriented event sourcing

grdscrc

#!/usr/bin/env bash
# Tested with jq 1.6 & fzf 0.42.0
# Inspired by https://github.com/reegnz/jq-zsh-plugin
# Call with `jazz <big_file_with_many_paths>.json` or `<command producing a valid json> | jazz`
# End command with `... | pbcopy` or `... > output.json` to save selection

input=$1

TMP_DIR=$(mktemp -d /tmp/jazz_XXX)
chmod 700 "$TMP_DIR"

lbialy

//> using lib "com.softwaremill.sttp.openai::core:0.0.6"

object ai:
  import scala.quoted.*
  import sttp.openai.OpenAISyncClient
  import sttp.openai.requests.completions.chat.*
  import sttp.openai.requests.completions.chat.ChatRequestBody.ChatBody
  import sttp.openai.requests.completions.chat.ChatRequestBody.ChatCompletionModel

  opaque type GPT[A <: String] <: String = String

lukepighetti

[keys.normal]
C-f = [":new", ":insert-output lf-pick", ":theme default", "select_all", "split_selection_on_newline", "goto_file", "goto_last_modified_file", ":buffer-close!", ":theme tokyonight_storm"]

Kirill255

Проверять метод на скрытость, можете тут: vk.com/dev/МЕТОД

gregberns

Introduction to Yoneda and Coyoneda

Yoneda (and its duel Coyoneda) is well known in the Category Theory field and has been ported over to functional languages such as Haskell. Each have their uses - sometimes in similar scenarios, also in very different ways.

This will be a newbie's explanation of the concept, using Haskell to illustrate, without any Category Theory.

From what I've read, the Yonedas are not 'daily-drivers' (not used everyday), but rather can be pulled out when the time is right.

Uses: Both Yoneda's can be used to help speed up a program where there are many fmap with long lists or big trees involved. Coyoneda can be used if you want to create an 'interface' and build up calculations, then pass those calculations to an 'executor' to run them.

munrocket

// copy paste this in console
function shader_exporter(duration, width, heigth, paused) {
  document.getElementById('demogl').style.width = width + 'px';
  document.getElementById('demogl').style.height = heigth + 'px';
  document.getElementById('myResetButton').click();
  document.getElementById('myRecord').click();
  if (paused) document.getElementById('myPauseButton').click();
  let t0 = performance.now();
  function loop(){
    if (performance.now() - t0 > duration * 1000) {

DareFox

    — Да?
    — Алё!
    — Да да?
    — Ну как там с деньгами?
    — А?
    — Как с деньгами-то там?
    — Чё с деньгами?
    — Чё?
    — Куда ты звонишь?

MichaelCurrin

Get GitHub Files

Get the metadata and content of all files in a given GitHub repo using the GraphQL API

You might want to get a tree summary of files in a repo without downloading the repo, or maybe you want to lookup the contents of a file again without download the whole repo.

The approach here is to query data from GitHub using the Github V4 GraphQL API.

About the query