I'd like to suggest that anyone who says Copilot saves them time is an indication that they're not doing their job, ie accepted the code without taking the time to think through each line and its implications.
To properly review code, you have to consider for each variable, each expression, whether it's appropriate, how it interacts with the rest of the program, etc.
Since you didn't author the code I'd say this should take more time than if you wrote it yourself.
If you work with text data in R, the gregexpr() function is essential for pattern matching. It finds all occurrences of a pattern within a string. Key parameters include pattern, text, ignore.case, perl, fixed, and useBytes. You can match characters, ignore case, use advanced regex, and search fixed strings.
Nowadays terminals and other text views can get rendered with GPU acceleration support, like the kitty terminal that I use.
🤔 That means we could get bloom, chromatic aberration, distortion, depth of field and other post process effects into our terminals, what are we waiting for?
Don’t miss the chance to participate in the Erlang Workshop!
The Erlang Workshop brings together the open source, academic, and industrial communities of Erlang, other BEAM-related languages, actor model programming, distribution, and concurrency to discuss techniques, technologies, languages, and other relevant topics.
Important dates:
Paper submission: May 30
Notification: June 27
Camera Ready: July
Not many people know about bleh debugging.
It's a technique I use when I want to check whether a certain piece of code is being compiled at all, such as if it's been ifdef'd out.
It works by inserting the following keyword in the piece of code you're looking at:
bleh
This is a special word that triggers an error in compilers of all programming languages, resulting in a message like "error: 'bleh' undeclared" if the code gets compiled. If not, the code is compiled out.