digikar99

Coalton: Why is the interop not easier, and why might it be necessary for Coalton to be an entire language in itself?

If you came here searching for the context in which some reddit comments were written, you might want to check out this previous version of the article.

Several blog posts have been written about Coalton, about how it can be useful and what it brings to the table. However, to me, it hasn’t been clear why Coalton is the way to solve the problems that it does solve. Isn’t a simpler solution possible without making a full embedded language, and giving users the cognitive overhead of thinking about interop between normal lisp and coalton?

I have been thinking about this for a while as one of my pasttimes, and below I’ll summarize the better reasons why coalton might be the way it is. Perhaps, I couldn’t se

brendanzab

September 2022:

This has spread to a far wider audience than I had anticipated - probably my fault for using a title that is in hindsight catnip for link aggregators. I wrote this back in 2021 just as a bunch of personal thoughts of my experiences using Rust over the years (not always well thought through), and don't intend on trying to push them further, outside of personal experiments and projects.

Managing a living language is challenging and difficult work, and I am grateful for all the hard work that the Rust community and contributors put in given the difficult constraints they work within. Many of the things I listed below are not new, and there's been plenty of difficult discussions about many of them over the years, and some are being worked on or postponed, or rejected for various good reasons. For more thoughts, please see my comment below.

My personal list of Rust gr

cgrand

Quick notes on how the fallback pseudo-type is used in cljd (ClojureDart).

Like cljs, cljd is built on protocols. Like in clj, each protocol is backed by an interface for the fast path. Let's call this interface the direct interface.

Cljd protocols are also backed by a second interface used for extensions to 3rd-party classes. Let's call this interface the extension interface.

Protocols are reified as instances of an IProtocol interface:

// emitted code

roman01la

(ns user
  #?(:cljs (:require-macros [user])
     :clj (:require [cljs.source-map :as sm]
                    [clojure.data.json :as json]
                    [clojure.java.io :as io]
                    [clojure.string :as str]
                    [cljs.env :as env])))

#?(:clj
   (defn map-location [env form & {:keys [offset]}]

pirate

#!/usr/bin/env bash
# This is a script that provides infinite history to get around Alfred's 3-month limit.
# It works by regularly backing up and appending the items in the alfred db to a
# sqlite database in the user's home folder. It also provides search functionality.

# https://www.alfredforum.com/topic/10969-keep-clipboard-history-forever/?tab=comments#comment-68859
# https://www.reddit.com/r/Alfred/comments/cde29x/script_to_manage_searching_backing_up_and/

# Example Usage:
#    alfred-clipboard.sh backup

dvdbng

import os
import re


def zsh_to_fish(cmd):
    return (cmd.replace('&&', '; and ')
               .replace('||', '; or '))


def is_valid_fish(cmd):

jcomellas

  # Given a module defined in this way:
defmodule HL7.Composite do
  # [...]
  defmodule EI do
    use HL7.Composite.Def

    composite do
      component :id,                type: :binary, default: ""
      component :namespace_id,      type: :binary, default: ""
      component :universal_id,      type: :binary, default: ""

oakes

Contents

• Why care about Rust?
• The Toolchain
• Creating a New Project
• Modules
• Crates
• Types
• References
• Mutability

unclebob

Today I gave a keynote at ACCU in Oxford.  In the midst of it I made two (count them) two statements that I should have known better than to make.  I was describing the late '70s, and the way we felt about the C language at the time.  My slide said something like: "C was for real men."  Emily Bache, whom I know and hold in high regard, spoke up and said "What about women?".  And I said something like: "We didn't allow women in those days."  It was a dumb crack, and should either not have been said, or should have been followed up with a statement to the effect that that was wrong headed.  

The second mistake I made was while describing Cobol. I mentioned Adm. Grace Hopper.  I said something like "May she rest in peace."  I don't know that any of the words were actually demeaning, but the tone was not as respectful as it should have been to an Admiral in the United State Navy, and one who was so instrumental in our industry; despite what I feel about Cobol.  

I am a 59 year old programmer who was brought up 

stuarthalloway

;; Datomic example code
;;
;; The extent of entity ?x is all datoms that are about ?x.
;; Drop this into your rules.
;;
;; Demonstrates
;;
;; 1. recursive query (extent calls itself)
;; 2. disjunction (different extent bodies are ORed)
;; 3. component attributes (e.g. your arm is a component, your brother isn't)