Dima
Dima
or mine
klimi
bon apetit
Anonymous
im waiting for you dimka :)
Anonymous
isnt there anyone who can help me for free?
Surge.rs
Anonymous
ahaha im learning to write c code :(
Anonymous
cant anyone help? i want to learn...
klimi
Ruuude
klimi
I have the right to warn you
Surge.rs
cant anyone help? i want to learn...
Learning is struggling for hours trying to figure some shit out. Not giving up and begging in a group chat to show you the answer
Surge.rs
No one here wants to answer college questions. Figure it out like all of us have done in the past
Anonymous
oke...
Anonymous
{
"user_action": "ui error",
"request": "App crash, UI failure",
"content_language": "GB",
"service": "none",
"package": "org.schabi.newpipe",
"version": "0.17.3",
"os": "Linux Android 7.1.1 - 25",
"time": "2020-01-09 00:16",
"exceptions": [
"java.lang.ArrayIndexOutOfBoundsException: length=25; index=-1\n\tat java.util.ArrayList.get(ArrayList.java:413)\n\tat org.schabi.newpipe.fragments.list.search.SuggestionListAdapter.getItem(SuggestionListAdapter.java:79)\n\tat org.schabi.newpipe.fragments.list.search.SearchFragment.getSuggestionMovementFlags(SearchFragment.java:927)\n\tat org.schabi.newpipe.fragments.list.search.SearchFragment$1.getMovementFlags(SearchFragment.java:304)\n\tat android.support.v7.widget.helper.ItemTouchHelper$Callback.getAbsoluteMovementFlags(ItemTouchHelper.java:1593)\n\tat android.support.v7.widget.helper.ItemTouchHelper.checkSelectForSwipe(ItemTouchHelper.java:991)\n\tat android.support.v7.widget.helper.ItemTouchHelper$2.onInterceptTouchEvent(ItemTouchHelper.java:351)\n\tat android.support.v7.widget.RecyclerView.dispatchOnItemTouchIntercept(RecyclerView.java:2932)\n\tat android.support.v7.widget.RecyclerView.onInterceptTouchEvent(RecyclerView.java:2978)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2210)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2748)\n\tat android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2385)\n\tat com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:437)\n\tat com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1834)\n\tat android.app.Activity.dispatchTouchEvent(Activity.java:3070)\n\tat android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:69)\n\tat android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:69)\n\tat com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:399)\n\tat android.view.View.dispatchPointerEvent(View.java:10377)\n\tat android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:4943)\n\tat android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4802)\n\tat android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4308)\n\tat android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4361)\n\tat android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4327)\n\tat android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4474)\n\tat android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4335)\n\tat android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4531)\n\tat android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.
Surge.rs
that stacktrace
Artöm
Its C xhat btw, consider searching for java one
Anonymous
hi
Anonymous
Anonymous
i dont know why the position of the value of i and x will be changed
Sasuke
Anonymous
i see
Sasuke
First use X and then i
Anonymous
I did it on purpose
Anonymous
I feel very confused
Anonymous
the gcc shouldnt do that
Anonymous
it changed the position of the value
Sasuke
What you wanted to do?
Anonymous
it can gives me a warning but shouldnt change the position or may cut the lenght
Sasuke
To cut the length you have to do it
Sasuke
Gcc won't do that it can't change anything apart from rules
Anonymous
Anonymous
do u find some rules?
Artöm
i dont know why the position of the value of i and x will be changed
It can happen if they are passed in registers and one is integral and other is floating point
Somya
Artöm
nullptr
Pro
Yakov
I’m gay
Artyom
Me 2
Surge.rs
EXCEPT I TOLD YOU THAT —-> LINUX <—— IS UP TO DATE
Are you serious? The kernel is one part. It gets released when torvalds chooses to release it. Theres no other software and people can choose what kernel they want. Some like support, some like kernel hacking, some are developing for a specific branch, and some like bleeding edge, youre sounding like a lunatic that is getting confused with distros
Ludovic 'Archivist'
Are you serious? The kernel is one part. It gets released when torvalds chooses to release it. Theres no other software and people can choose what kernel they want. Some like support, some like kernel hacking, some are developing for a specific branch, and some like bleeding edge, youre sounding like a lunatic that is getting confused with distros
Don't mind him, he is that a lunatic
Surge.rs
That was entertaining as hell to reread. Life lessons and coding best practices from a 16 year old
Surge.rs
Never thought I'd see the day where someone who can barely work 40 hours a week legally thinks he knows literally everything about something so diverse
Ludovic 'Archivist'
That was entertaining as hell to reread. Life lessons and coding best practices from a 16 year old
He used to be half decent before he decided to switch to getting taught programming by a schizophrenic
Surge.rs
He used to be half decent before he decided to switch to getting taught programming by a schizophrenic
Oh yeah that'll do it
Anonymous
`ostream & operator <<(ostream &os, Test &r)
{
os<<"\n"<<r.h;
return o;
}`
Why don't we just return os? If os is the reference to cout then why again return reference to os? Isn't reference to os same as refererence to cout?
Mar!o
You meant return os right?
Mar!o
Well look cout is just a global variable of the type ostream
Mar!o
Maybe someone has their own variable and it that would not work if we return cout
Anonymous
Maybe someone has their own variable and it that would not work if we return cout
I didn't get that
Anonymous
I have a question, when we return by value, the copy of the returned object is created and then that copy is returned so is copy constructor called during this copying?
Mar!o
I have a question, when we return by value, the copy of the returned object is created and then that copy is returned so is copy constructor called during this copying?
Yep but either the object gets moved or with rtvo (return value optimization) this copy gets eleminated (except maybe for primitives)
Mar!o
I didn't get that
Well we should always stick to the object with which the operator was called. What if multiple exist and we always return cout we might return the wrong object because it was called on something else
Anonymous
Also what is the lifetime of the newly created copy?
Surge.rs
Also what is the lifetime of the newly created copy?
Depends if it's a deep copy or a shallow copy if I'm not mistaken
Anonymous
Depends if it's a deep copy or a shallow copy if I'm not mistaken
Well, when we return by value, how do we know whether it is deep/shallow?
Surge.rs
If it's a single value being returned that gets stored in some variable it will have the lifetime of the variable
Surge.rs
It's different for objects and I'm vague on exactly what it does. Lemme find a source
Surge.rs
Well, when we return by value, how do we know whether it is deep/shallow?
http://www.fredosaurus.com/notes-cpp/oop-condestructors/shallowdeepcopy.html
Mar!o
Well, when we return by value, how do we know whether it is deep/shallow?
It depends if it is a pure value or a dynamic allocated object/pointer/reference/rvalue ref
Artöm
Well, when we return by value, how do we know whether it is deep/shallow?
C++ I suppose? Usually custom copyctor implements deep copy, or if fields are either trivial or have custom copyctors
Artöm
user-provided's the name
Francisco
Well, when we return by value, how do we know whether it is deep/shallow?
In C++ you don't usually talk in those terms. An object itself can be copyed (deep copy) or moved (transfer all the contents of the objecto to another, leaving the first one empty). A shallow copy is what in C++ we call a reference (kind of), because it's the same object, just with another name
Francisco
A reference is just a pointer behind the scenes, just to make programmers lifes easier
xQuantx
Hi Moritz
Anonymous
....
Anonymous
any one there?