org | My brain in plain text | Wiki library

I'm unsure if the problem is my code or if I found a compiler bug.

The problem is your code. In GNU assembler, parentheses are used to dereference like unary * is in C, and you can only dereference a register, not memory. As such, writing 12(%0) in the assembly when %0 might be memory is wrong. It only happens to work in GCC because GCC chooses to use a register for "rm" there, while Clang chooses to use memory. You should use "r" (bytes) instead.

Also, you need to tell the compiler that your assembly is going to modify the array, either with a memory clobber or by adding *(unsigned char (*)[16])bytes as an output. Right now, it's allowed to optimize your printf to just hardcode what the values were at the beginning of the program.

Fixed code:

I think the main misunderstanding is that my Int @a = 1,2,3 and [1,2,3] are somehow equivalent. They are not. The first case defines an array that will only take Int values. The second case defines an array that will take anything, and just happens to have Int values in it.

I'll try to cover all versions you tried, why they didn't work, and possibly how it would work. I'll be using a bare dd as proof that the body of the function was reached.

#1

My research of the major syntax and functionality differences from http://www.greenend.org.uk/rjk/tech/regexp.html:

• . in GNU grep does not match null bytes and newlines (but does match newlines when used with --null-data), while Perl, everything except \n is matched.
• [...] in GNU grep defines POSIX bracket expressions, while Perl uses "character" classes. I'm not sure on the details. See http://www.greenend.org.uk/rjk/tech/regexp.html#bracketexpression
• "In basic regular expressions the meta-characters ?, +, {, |, (, and ) lose their special meaning; instead use the backslashed versions \?, \+, \{, \|, \(, and \)." From https://www.gnu.org/software/grep/manual/html_node/Basic-vs-Extended.html. ERE matches PCRE syntax.
• GNU grep \w and \W are the same as [[:alnum:]] and [^[:alnum]], while Perl uses alphanumeric and underscore.
• GNU grep has \< and \> for start and end of word.

Perl supports much more additional functionality:

• "nongreedy {}" with syntax re{...}?
• additional anchors and character types \A, \C, \d, \D, \G, \p, \P, \s, \S, \X. \Z, \z.
• (?#comment)
• shy grouping (?:re), shy grouping + modifiers (?modifiers:re)
• lookahead and negative lookahead (?=re) and (?!re), lookbehind and negative lookbehind (?<=p) and (?
• Atomic groups (?>re)
• Conditional expression (?(cond)re)
• ... and more, see man pcresyntax

The error messages states that the service account does not have the permission compute.disks.list.

What permissions does the role roles/resourcemanager.organizationViewer have?

You shouldn't necessarily have to implement a full custom atomic API, it should actually be safe to simply pull out a pointer to the underlying data from the atomic and pass it to the system.

Since std::atomic does not offer some equivalent of native_handle like other synchronization primitives offer, you're going to be stuck doing some implementation-specific hacks to try to get it to interface with the native API.

For the most part, it's reasonably safe to assume that first member of these types in implementations will be the same as the T type -- at least for integral values ^[1]. This is an assurance that will make it possible to extract out this value.

... and casting std::atomic to u/int* is UB

It seems you're mixing up Spark's split method for Columns with Scala's split for Strings. Please see example below for how the two different split methods are used. Method array_intersect is for intersecting the split Array column with the split element-filter string.

You can use a type predicate to define a user-defined type guard like this:

The best I have so far is { person: message.person, tag: 1 }.

Is there shorthand initializer syntax to achieve this?

Well, it's indeed not possible that declarative way since we don't have hook for injecting to the reactive type in the middle on that level.