People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
$/
artifacts/
build/
docs/
lib/
packages/
samples/
src/
tests/
| /** | |
| * This are a collection of examples for C 201. | |
| * These combine concepts you may or may not be | |
| * familiar with and are especially useful for | |
| * students new to C. There is a lot of really | |
| * cool stuff you can do in C without any cool | |
| * languages. | |
| * | |
| * This is file in particular is an introduction | |
| * to fun function usage in C. |
State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?
There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.
Here I present a composable pattern for pure state machiness with effects,
Maintaining mutual consistency across different sites, on updates, insertion and deletions, when a database is replicated is non-trivial and a significant problem. Though, it sounds reasonable to maintain a list of all replication servers and send direct updates to all when an update occurs at a site, it can cause large network load on the link of the node that has the initial update. Also, in case of constantly adding and leaving nodes, maintaining a consistent list of a million or a few hundered thousand nodes at every site consistently itself is difficult. In the face of the above mentioned problems, the algorithms described in the paper can come in handy.
The described algorithms have been used in the clearinghouse servers of the Xerox Corporate Internet and have proven to be very useful.
| # Viktor Dukhovni's (@vdukhovni) slow rebase, made faster by bisecting, sort of | |
| # | |
| # fastrebase BRANCH_TO_REBASE ONTO | |
| function fastrebase { | |
| typeset b N | |
| if (($# > 0)) && [[ $1 = -h || $1 = --help ]]; then | |
| printf 'Usage: fastrebase BRANCH_TO_REBASE ONTO_HEAD\n' | |
| printf ' fastrebase # to continue after resolving conflicts\n' | |
| printf '\n\tfastrebase is a shell function that uses the following\n' |
| # Check these threads before proceeding: | |
| # https://github.com/microsoft/WSL/discussions/5857 | |
| # https://github.com/microsoft/WSL/issues/5821 | |
| if (-Not ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] 'Administrator')) { | |
| $CmdLine = "-File `"" + $MyInvocation.MyCommand.Path + "`" " + $MyInvocation.UnboundArguments | |
| Start-Process -FilePath PowerShell.exe -Verb Runas -ArgumentList $CmdLine | |
| Exit | |
| } | |
| # Restart the Host Network Service | |
| Restart-Service -Force -Name hns |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
I want Microsoft to do better, want Windows to be a decent development platform-and yet, I constantly see Microsoft playing the open source game: advertising how open-source and developer friendly they are - only to crush developers under the heel of the corporate behemoth's boot.
The people who work at Microsoft are amazing, kind, talented individuals. This is aimed at the company's leadership, who I feel has on many occassions crushed myself and other developers under. It's a plea for help.
You probably haven't heard of it before, but if you've ever used win32 API bindings in C#, C++, Rust, or other languages, odds are they were generated from a repository called microsoft/win32metadata.