1,261 karma · joined May 2, 2016
Are there any common resources for this kind of access methods and patterns that specifically aim to bridge the soft-/hardware gap? The best one I can come up with is Performance Analysis and Tuning on Modern CPUs[0] by Denis Bakhvalov.
EDIT: Ok, there is, but it needs a query...
If you wish to quote me, then do it accordingly: the AfD is blaming the established democratic processes for the current "cartel" situation. As if that's the only thing to blame, and not that the AfD is not willing to collaborate with other democratic parties or even respect the democratic process.
A popularity in election results doesn't define a parties position on the political spectrum. A lot of people are voting for change to occur, but that doesn't mean that that change already happened just by counting the votes.
It's actually quite the opposite, they are running on things like a direct democracy[0], with phrases such as "Wir sind überzeugte Demokraten"[1] (eng: We are confident democrats). And they do that for good reason, as running a party that openly wants to abandon the democratic process would be against the constitution.
[0]: https://de.wikipedia.org/wiki/Alternative_f%C3%BCr_Deutschla...
[1]: https://www.afd.de/wp-content/uploads/2018/01/Programm_AfD_D...
I only get shown the login prompt when the network connection to my server isn't established yet. I'm on Wi-Fi and need to wait for the connection before launching the client.
[0]: https://docs.python.org/3/library/typing.html#typing.assert_...
There's a big difference in ambiguousness and ambivalence, especially in documentaries. "Ambiguousness" represents an uncertain logical conclusion, whereas "ambivalence" stands in for (the strength of) conflicting forces.
I'd wager that an ambiguous documentary would be close to being unwatchable, and I can't remember that I've seen any. Since I've yet to see You Can See Everything, unfortunately I can't comment about it in any way.
That's the Right of withdrawal[0] by EU law, though. Do you mean something else?
I mean, sure, smaller shops might not cover the costs for the return shipping, but I don't really mind.
[0]: https://europa.eu/youreurope/citizens/consumers/shopping/ret...
Even worse, by splitting one state (and one derivable category from that state) into two separate arguments for do_thing, something can be off rather badly. I'd then feel the need to design an assertion of the relation of the arguments in order to make things bearable again:
def do_thing(category, data):
# to avoid shadowing lets rename your function `category` to `category_from_item`
assert all(category == category_from_item(item) for item in data)
...
But that would add a third loop to your two loops, and would duplicate the computation of a category.Instead, if category would be a property of data item:
class DataItem:
@property
def category(self):
...
...and the do_thing function would work on a single data item, then it'd just become a simple matter of one for loop and one match/case: def do_thing(item):
match item.category:
case ...:
...OP is talking about type stripping nonetheless, and I'd put type stripping into the same ballpark as reading ambient declarations, performance wise.
> Node.js ignores tsconfig.json files and therefore features that depend on settings within tsconfig.json, such as paths or converting newer JavaScript syntax to older standards, are intentionally unsupported.
Of course import aliases and such features would break.
OP doesn't want the types to be checked, they want the types to be stripped. Type stripping ignores tsconfig.json files and any of its features, see: https://nodejs.org/api/typescript.html#type-stripping