Summary: all crates that the lint triggered on contained actual UB (both in Stacked Borrows and in Tree Borrows). Not all instances are UB (some are only reads), though, but this clearly show the pattern is dangerous. However, there are some popular crates that do that.
Most are conversions from &NonAtomic to &Atomic.
The critical few things you need to know about it are:
Update: I've been told by representatives of the Scala Center at EPFL that sharing the information below on the Scala Contributor list is a violation of the Scala Code of Conduct and could result in a ban.
This document contains some quotations by "sken", an active contributor to ZIO and member of the ZIO community. This individual uses the name Lorca in various places, including his first and longest-lived Twitter handle, and will be referred to as Lorca throughout this document. All of the information below is publicly available and easily linked to Lorca.
Note that all of the tweets below would have been visible to the other ZIO community members who regularly interacted with Lorca via the same Twitter account, including John De Goes, the CEO of [Ziverge](https://ziverge
| #!/bin/bash | |
| set -e | |
| # Simple script to remove dangling images from GHCR. | |
| # You need to have installed gh cli and jq for this script to work properly | |
| # You need to be logged to 'gh' first | |
| container="debian/buildd" | |
| temp_file="ghcr_prune.ids" | |
| rm -rf $temp_file |
(If this file is included in a project, you can find the list of current caretakers at the bottom.)
In a small classical open-source project, maintainers do a lot, and if maintainers don't have time to do a lot, usually the project stalls. Finding new maintainers is hard because few people actively want to take over all the responsibilities of a project. There must be a different way.
With Caretaker Maintainership, "Maintainers" become "Caretakers". Caretakers' only mandatory responsibility is to grant Releasers commit and publish access to the project.
| <link rel="shortcut icon" width=32px> | |
| <canvas style="display: none" id="loader" width="16" height="16"></canvas> | |
| <script> | |
| class Loader { | |
| constructor(link, canvas) { | |
| this.link = link; | |
| this.canvas = canvas; | |
| this.context = canvas.getContext('2d'); | |
| this.context.lineWidth = 2; |
| #!/usr/bin/awk -f | |
| # This program is a copy of guff, a plot device. https://github.com/silentbicycle/guff | |
| # My copy here is written in awk instead of C, has no compelling benefit. | |
| # Public domain. @thingskatedid | |
| # Run as awk -v x=xyz ... or env variables for stuff? | |
| # Assumptions: the data is evenly spaced along the x-axis | |
| # TODO: moving average |
Here's how my level implementing Portal in Baba is You works! If you haven't seen it, here's a video: https://streamable.com/9pflr
Baba is You is a game played with the arrow keys. How can Baba fire a portal gun and still have the ability to walk around? The answer: there's one more button the game allows, and that's the wait button - which makes baba stand still and allows a turn to pass in the game world. In this level, the wait button does more than wait - it fires the portal gun.
The skull crosses are a gadget to activate an arbitrary rule when the wait button is pressed. The following rules are used to set it up:
FUNGUS MAKE BABA
BABA ON FUNGUS IS MOVE AND MOVE
BABA ON SKULL IS EMPTY
Why?
This:
.action {
@extend .ml-3;
}
| // ==UserScript== | |
| // @name BTD from_list mute filter | |
| // @namespace http://tampermonkey.net/ | |
| // @version 0.1 | |
| // @description mm | |
| // @author You | |
| // @match https://tweetdeck.twitter.com | |
| // @grant none | |
| // ==/UserScript== |