Flow doesn’t do direct casting from one type to another, but you can do something like const bar: string = (foo: any); so you cast foo to an any, because any accepts any type of value as an input. Then because the any type also allows you to read all possible types from it, you … Read more
Just use int(): x := float32(3.1) fmt.Println(int(x)) Which produces 3 as needed, without having to use string conversions or the like.
It is very easy to write a Benchmark test to check it: http://play.golang.org/p/E9H_4K2J9- package main import ( “testing” ) type myint int64 type Inccer interface { inc() } func (i *myint) inc() { *i = *i + 1 } func BenchmarkIntmethod(b *testing.B) { i := new(myint) incnIntmethod(i, b.N) } func BenchmarkInterface(b *testing.B) { i := … Read more
There are 4 possible conversion methods in TypeScript for arrays: let x = []; //any[] let y1 = x as number[]; let z1 = x as Array<number>; let y2 = <number[]>x; let z2 = <Array<number>>x; The as operator’s mostly designed for *.tsx files to avoid the syntax ambiguity.
You can’t do it in a single line. Your temporary variable approach is the way to go. By the way, is it called casting when it comes to interfaces? It is actually called a type assertion. A type cast conversion is different: var a int var b int64 a = 5 b = int64(a)
You can use the Float() initializer: let cgFloat: CGFloat = 3.14159 let someFloat = Float(cgFloat)
This is either a bug in TypeScript or a concious design decision, but you can work around it using: var myBool: bool = true; var myString: string = String(myBool); alert(myString); In JavaScript booleans override the toString method, which is available on any Object (pretty much everything in JavaScript inherits from Object), so… var myString: string … Read more
Update: This answer was the best solution in earlier versions of TypeScript, but there are better options available in newer versions (see other answers). The accepted answer works and might be required in some situations, but have the downside of providing no type safety for building up the object. This technique will at least throw … Read more
The problem is that when the type is inferred, then the type of o is: { dic: { a: number, b: number } } That’s not the same as { dic: { [name: string]: number } }. Critically, with the top signature you’re not allowed to do something like o.dic[‘x’] = 1. With the 2nd … Read more
Converting values From a type that fits completely within another There’s no problem here. Use the From trait to be explicit that there’s no loss occurring: fn example(v: i8) -> i32 { i32::from(v) // or v.into() } You could choose to use as, but it’s recommended to avoid it when you don’t need it (see … Read more