Digital nomad
Anything related to I/O 💻
Keep in mind, particularly with objects and arrays you can achieve immutability with object and array spread operators respectively as follows : With objects: let a = { x : 1 } let b = {...a} b.x = 2 ; console .log(a.x) // still x === 1 With arrays : let a = [ "one" ] let b = [...a] b[ 0 ] = "two" ; console .log(a.x) // still outputs as "one" Cheers !
Missing some TL;DR : == for values ( auto type conversion between comparisons are done internally) , whereas === for type AND value, whereas type takes precedence over value, if type does not match to, it short-circuits which leads to optimisation whatsoever . Please correct if I am wrong . Thank you .
Nice one ! Also consider example with simple under(lying) type package main import ( . "fmt" ) type under int // Based on (but with underlying type) : @https://blog.harishdurga.com/the-three-dots-in-golang // define ...rest like parameter for variadic functions func Sum (nums ...under) under { var r under = 0 for _, n := range nums { r += n } return under(r) } func main () { /* Println( Sum([]int{1,2,3}...) ) */ // instead do: Println( Sum([]under{ 1 , 2 , 3 }...) ) }
@Tomasz Węgrzanowski useful as usually. Personally I am Windows user as I think Win10 suits my dummy will, but I see Git for Windows offers quite small range of capabilities in terms of file system management . I'd like to hear your opinion on WSL if you spared a minute . Do you think it's a MUST to have on a machine of Win10 user if I exploit Node.js on a daily basis ?.. Thanks !