xedin
Re:New Diagnostic Architecture Overview
on Thursday October 17, 2019 @07:22PM (#21287270)
This is the diagnostic produced for similar example using new diagnostic architecture:
error: binary operator '+' cannot be applied to operands of type 'String' and 'Int'
_ = "a" + 1
~~~ ^ ~
note: overloads for '+' exist with these partially matching parameter lists: (Int, Int), (String, String)_ = "a" + 1
^
note: candidate expects value of type 'String' for parameter #2 @inlinable public static func + (lhs: String, rhs: String) -> String
^
note: candidate expects value of type 'Int' for parameter #1 public static func + (lhs: Int, rhs: Int) -> Int
^
Re:New Diagnostic Architecture Overview
on Thursday October 17, 2019 @06:13PM (#21286834)
There is a discussion about introducing "descriptive" diagnostics of the same style happening on the Swift Forums at the moment - https://forums.swift.org/t/pitch-extended-error-messages-dia....
I this it's a great idea and with new diagnostic architecture described in the blog post it would be relatively easy to archive.
Re:New Diagnostic Architecture Overview
on Thursday October 17, 2019 @04:49PM (#21286236)
Yes, SwiftUI diagnostics in particular are going to benefit from these changes.
Re:Java 8 Library for Building High-Performance, Thread-Per-Core Appli...
on Saturday February 20, 2016 @02:17AM (#11139254)
Yes, exactly since it allows for fewer context switches and cache locality not only for the network packets but for disk I/O as well.
Re:Java 8 Library for Building High-Performance, Thread-Per-Core Appli...
on Thursday February 18, 2016 @11:25PM (#11131528)
It uses Thread-Per-Core architecture where Netty/Reactor use thread-pools to process work and have dedicated threads for selecting from network.