activcoding

import Foundation

/// FuzzySearchCharacters is used to normalise strings
struct FuzzySearchCharacter {
    let content: String
    // normalised content is referring to a string that is case- and accent-insensitive
    let normalisedContent: String
}

/// FuzzySearchString is just made up by multiple characters, similar to a string, but also with normalised characters

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

ChristianKienle

public struct Promise<T> {
  typealias Fulfiller = (T) -> (Void)
  typealias Rejecter = (Void) -> (Void)
  typealias Resolver = (_ fulfill: @escaping Fulfiller, _ reject: @escaping Rejecter) -> (Void)
  let resolver: Resolver
  init(_ resolver: @escaping Resolver){
    self.resolver = resolver
  }
  func then<U>(_ execute: @escaping ((T) -> U)) -> Promise<U> {
    return Promise<U>({(fulfill, reject) in

alirobe

### 
###
### UPDATE: For Win 11, I recommend using this tool in place of this script: 
### https://christitus.com/windows-tool/
### https://github.com/ChrisTitusTech/winutil
### https://www.youtube.com/watch?v=6UQZ5oQg8XA
### iwr -useb https://christitus.com/win | iex
###
###

erica

Remove C-style for-loops with conditions and incrementers

• Proposal: SE-NNNN
• Author(s): Erica Sadun
• Status: Review
• Review manager: TBD

Introduction

The C-style for-loop appears to be a mechanical carry-over from C rather than a